On Fri, 30 Mar 2007, Guennadi Liakhovetski wrote: > > > > > > How about suggesting "clone -l -s"? > > Yes, but how do "advanced git users" kernel developers work? Do they just > do 1 clone and build / clean every time they want to test another > configuration / arch, or do they clone -l or what? Do they create branches > for each development thread, then pull / push between trees?... I suspect it depends on the developer. I end up just using different branches and switching between them, but then, my branches tend to all be pretty small test-stuff (I only end up using one main branch, since 99% of what I do is merge other peoples stuff that has already gone through a test-cycle). > But I don't want to re-build. Apart from i386 I build for a couple of ARM > and PPC targets too... You're probably fine with "git clone -l -s" then. > Strange. Is my git 1.4.0 criminally broken? I have a clone of Linus' tree > on a USB disk on ext3 without any objects, which I just cloned at some > point and then did a couple of pulls from the same source. Now > > 1545084 /mnt/sda2/kernel-git/linux-2.6/ > 1255084 /mnt/sda2/kernel-git/linux-2.6/.git The old git that always exploded all pulls and generated lots of loose objects? You can check with "git count-objects". And to fix it, just do a "git gc" (or with older git versions, the secret handshake is just a simple "git repack -a -d"). > But that's a freshly cloned tree, without any pulls. I re-cloned it, > because the tree I had earlier had the problem with each pull: > > Unpacking 12452 objects > 100% (12452/12452) done > * refs/heads/origin: does not fast forward to branch 'master' of > git://git.kernel.org/pub/scm/linux/kernel/git/paulus/powerpc; > not updating. Sounds like either Paul re-based his tree, or you did some work on your "origin" branch.. Linus - 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