On Mon, 11 Jul 2005, Junio C Hamano wrote:
> Linus Torvalds <[EMAIL PROTECTED]> 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
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
*This .sig left intentionally blank*
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