On Thu, Nov 16, 2006 at 12:34:27PM CET, Alexandre Julliard wrote: > Junio C Hamano <junkio@xxxxxxx> writes: > > > I would rather say "use 'git branch' to make sure if you are > > ready to merge". Who teaches not to use "git pull"? > > We do that for Wine. The problem is that we recommend using git-rebase > to make it easier for occasional developers to keep a clean history, > and rebase and pull interfere badly. How do those developers submit their changes? Do they push? If they do, git-rebase can be saving one merge at most, and the merge is actually a good thing (someone should write some nice standalone writeup about that). If they don't have push access and maintain their patches locally until they get accepted, perhaps it would be far simpler for them to use StGIT? -- Petr "Pasky" Baudis Stuff: http://pasky.or.cz/ #!/bin/perl -sp0777i<X+d*lMLa^*lN%0]dsXx++lMlN/dsM0<j]dsj $/=unpack('H*',$_);$_=`echo 16dio\U$k"SK$/SM$n\EsN0p[lN*1 lK[d2%Sa2/d0$^Ixp"|dc`;s/\W//g;$_=pack('H*',/((..)*)$/) - 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