On Fri, Nov 17, 2006 at 01:27:53AM CET, Han-Wen Nienhuys wrote: > put clone would be the putative inverse of clone, ie. make a clone of > a local repository on a remote server. So effectively to tell git push not to unpack on the remote side, and to push all branches and relevant tags. ..snip.. > It's more logical for clone to either > > * leave all names unchanged > > * put all remote branches into a subdirectory. This would also make > it easier to track branches from multiple servers. > > At present, I have in my build-daemon the following branches, > > cvs-head-repo.or.cz-lilypond.git > hanwen-repo.or.cz-lilypond.git > hwn-jcn-repo.or.cz-lilypond.git > lilypond_1_0-repo.or.cz-lilypond.git > lilypond_1_2-repo.or.cz-lilypond.git > lilypond_1_4-repo.or.cz-lilypond.git > lilypond_1_6-repo.or.cz-lilypond.git > lilypond_1_8-repo.or.cz-lilypond.git > lilypond_2_0-repo.or.cz-lilypond.git > lilypond_2_2-repo.or.cz-lilypond.git > lilypond_2_3_2b-repo.or.cz-lilypond.git > lilypond_2_3_5b-repo.or.cz-lilypond.git > lilypond_2_4-repo.or.cz-lilypond.git > lilypond_2_6-repo.or.cz-lilypond.git > lilypond_2_8-repo.or.cz-lilypond.git > master-git.sv.gnu.org-lilypond.git > master-hanwen > master-repo.or.cz-lilypond.git > origin-repo.or.cz-lilypond.git > stable > stable-2.10 > stable--2.10-git.sv.gnu.org-lilypond.git > > It would solve lots of problems for me if cloning and fetching would > put branches into a subdirectory, ie. > > git clone git://repo.or.cz/lilypond.git > > leads to branches > > repo.or.cz/lilypond_2_8 > repo.or.cz/lilypond_2_6 > repo.or.cz/lilypond_2_4 > repo.or.cz/master > (etc..) That's basically exactly what git clone --use-separate-remote should do. Now only if it would become the default... :-) -- 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