On Thu, Dec 07, 2006 at 01:23:00PM -0800, Junio C Hamano wrote: > Under my suggestion, the new git-checkout -b (and git-branch) > would: > > (0) proceed if there is an explicit branch point specified on > the command like, just like now; > > (1) allow omission of branch-point if the current branch has > allowbranchbydefault configuration set as in above. A new > branch is created forking off of the current HEAD; > > (2) allow omission of branch-point if no branch has such > configuration; in other words, existing repositories that > do not have the allowbranchbydefault configuration anywhere > are not affected. A new branch is created forking off of > the current HEAD; > > (3) otherwise, it barfs if you do not give an explicit > branch-point. > > and a newly created repository that is newbie friendly has one > such configuration automatically set for 'master' (if created > with git-init) or whatever the primary branch is (if created > with git-clone). That makes the default behavior more complicated to explain. Is there really sufficient evidence that this a serious problem? --b. - To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html