On Mon, 29 Aug 2005, Bryan O'Donoghue wrote:
> 
> If I'm understanding, I update to a given git repository, branch locally
> based on tags and then I can checkout a branch locally, to make that the
> active branch.

Exactly. This is the difference between a tag and a branch: a tag is an
"immobile" point in time, while branches are "heads of active development"
(there's a bit more detail to this: you _can_ change a tag, so it's not
like it's totally fixed in stone, but the point is that it's not a dynamic
entity - it's some fairly static thing that you've protected).

So you can't start new development off a tag directly: you need to create
a new branch that just starts off at the point that the tag points to.  
So if you really think of a branch as that "head of active development"
and tags as "static points in time" this all makes tons of sense.

Btw, you don't need to branch based on tags: you can branch based of _any_ 
kind of local reference. A tag is just a common one. But you can branch 
based on your current state too, ie a command line like

        git branch -b fixup HEAD^

means that you will create a "fixup" branch that starts not at a tag, but 
at the "parent of HEAD". In particular, let's say that you just committed 
something, and realized that you need to work on something else without 
the new thing disturbing you (you have a patch that applies in the same 
area, or whatever), something like the above works fine.

Or just use "gitk" to visually find a place, and when you decide to start 
a new branch somewhere, select that commit in gitk, and use the 
cut-and-paste facility to just paste the SHA1 directly into

        git branch -b working <any-random-point-sha1>

so it's not like the tags are important per se, they're just short-hand 
symbolc way-markers.

                        Linus
-
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at  http://vger.kernel.org/majordomo-info.html

Reply via email to