[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: base

From: David Robinow
Subject: Re: base
Date: Thu, 26 Aug 2010 11:11:09 -0400

On Thu, Aug 26, 2010 at 10:42 AM, Óscar Fuentes <address@hidden> wrote:
> For any dVCS, revision IDs are a core concept. A user that doesn't
> understand revision IDs eventually will suffer the consequences of his
> ignorance. That applies to git's SHA1 hashes and to whatever bzr uses as
> IDs. Blobs and trees are on the foundations of git and defines how it
> stores information. Having some knowledge about them makes easy to
> understand why git does not track empty directories, how file renaming
> is (un)supported, why some operations are blazingly fast but others
> (`annotate') are not, etc. The index is one of the most useful
> innovations of git. If you insist on ignoring its existence you are
> missing a really good feature. Almost every operation in git is about
> creating trees, blobs and updating pointers (refs). Do you want to see a
> file on another branch without switching to it? If you know about refs,
> trees and blobs, it is straightforward. Want to temporaly reset your
> working copy to some point on the past? If you know what a git ref is
> then you already know that it is possible. Refs are arranged on the file
> system on the same way you can name them (i.e. "git log
> refs/remotes/origin/master" will work fine)
> ...

Do you realize you are making an effective argument against using a
Distributed Version Control System?  If I had to go to auto mechanic
school to learn to drive, I'd probably take the bus.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]