On Mon, Feb 02, 2009 at 02:52:26PM +0100, Johannes Schindelin wrote: > > It looks like the consensus is to add a branch.master config section > > even when cloning an empty repo. And that should address my concern in > > the 99% of cases where people use the default "master" setup. Which kind > > of takes away the main use case for this topic. > > From where I sit, the main use would have been: > > # <hackhackhack> > $ git init > $ git add . > $ git commit -m initial\ revision > # <hackhackhack> > # <create a repository on repo.or.cz> > $ git remote add origin $URL > $ git push -t origin master Hmm. True. The "clone empty" fix only affects people who use the "init; clone empty; push" method. Push-tracking would work for the "traditional" method you outline above. So probably it is worth doing the steps I described earlier. I'll throw it on my todo list, but the priority is not especially high. > BTW I always wondered if it would make sense to introduce "git commit > --init" for the first 3 Git commands. I use them way too often. I have noticed that, too, but I think it is because I am constantly creating test repos to debug git. Regular users don't have the same problem. :) -Peff -- 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
