Re: Bootstrapping into git, commit gripes at me
- From
Daniel Barkalow <barkalow@iabervon.org>
- Date
- Jul 12, 2005, 17:04 UTC
- Message-ID
- <Pine.LNX.4.21.0507121240120.2876-100000@iabervon.org>
- In-Reply-To
- <7voe98g3ws.fsf@assigned-by-dhcp.cox.net>
On Mon, 11 Jul 2005, Junio C Hamano wrote:
Show 14 quoted lines
> Linus Torvalds <torvalds@osdl.org> writes: > > > But what about the branch name? Should we just ask the user? Together with > > a flag, like > > > > git checkout -b new-branch v2.6.12 > > > > for somebody who wants to specify the branch name? Or should we pick a > > random name and add a helper function to rename a branch later? > > > > Opinions? > > How about treating "master" a temporary thing --- "whatever I > happen to be working on right now"?
That conflicts with my usage, where I have a single repository for all of my working directories, with .git/refs and .git/objects being symlinks to it, but .git/HEAD being different for each branch. The stuff in objects/ and refs/ really shouldn't depend on what you're currently doing for this reason.
My way of thinking of "master" is that it's a real branch, which is for all of the situations where you aren't using a specially-designated branch. For many people, they only do stuff that's not designated specially; Jeff only does stuff that is designated specially. But if you do both, you'll want master to be left alone while you work on the side branch.
-Daniel *This .sig left intentionally blank*