Dear diary, on Fri, Oct 20, 2006 at 03:17:26PM CEST, I got a letter where Jakub Narebski <jnareb@xxxxxxxxx> said that... > But you can also clone _whole_ repository, _all_ published branches with > > $ cg clone git://git.kernel.org/pub/scm/git/git.git Nope, cg clone will in this case clone the master branch (or whatever the remote HEAD points at). cg clone -a is planned but not implemented yet. Very soon now, hopefully. :-) > In GIT to work on some repository you don't (like from what I understand > in Bazaar-NG) "checkout" some branch (which would automatically copy some > data in case of "heavy checkout" or just save some pointer to repository > in "lightweight checkout" case). You clone whole repository; well you can > select which branches to clone. "Checkout" in GIT terminology means to > populate working area with given version (and change in repository which > branch is current, usually). You don't need to, you can switch your working tree between various branches. I think Linus said he does that (or was it Junio?), and I do that as well, as well as many others. A good question would be "when to create another branch and when to clone the repository". And I don't think there's any good answer, except "when you are comfortable with it". :-) Both approaches have pros/cons. -- 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