Re: basics... when reading docs doesn't help

[Guennadi Liakhovetski <g.liakhovetski@gmx.de>]

On Thu, 29 Mar 2007, J. Bruce Fields wrote:

> On Thu, Mar 29, 2007 at 02:26:10PM -0700, Junio C Hamano 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?...

> If you really want to share as much as possible, then I guess you want
> to share the working trees too, since (as evidenced above), they're at
> least as large as the compressed history.

But I don't want to re-build. Apart from i386 I build for a couple of ARM 
and PPC targets too...

> Though actually on a second look, clone -l -s produces something that's
> only 377M.  I hadn't realized how much space the build output takes up.
> So judging from du the 1.5G Guennadi Liakhovetski mentions above seems
> to break down into something like:
> 
> 	330M .git
> 	380M working tree
> 	750M build output

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

Interestingly, both end up with 5084. For comparison:

465044  /mnt/sda2/kernel-git/powerpc
174980  /mnt/sda2/kernel-git/powerpc/.git

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.

Wonderful and strange git world...

Thanks
Guennadi
---
Guennadi Liakhovetski