On Mon, Jul 11, 2005 at 08:41:43PM -0700, Junio C Hamano wrote: > When I start working on something I often do not know what the > thing I am going to work on ends up to be. So I would start > from v2.6.12 tag, do random hacking, and when I got into a > reasonable shape, I would say ``Ok, this is worth saving. Let's > name it "foobar" branch and continue.'' And I would probably > switch to some other subproject when an urgent bugfix comes in, > and I would not want to lose my "master" _then_. So (the > "branch" one has been revised):
Isn't that what a tag is for? o Make a sandbox o Commit cool changes o Tag the last commit object o Throw sandbox away. o Push changes or generate patch based on the tag The change is that we can create a sandbox by giving it a starting point, a tag. If we decide we want to keep working on this branch, all we'd have to do is go back to that tag, although I admit it may seem sloppy to have to create a new branch from a tag'd commit that we originally part of a branch. - 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
