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

From: J. Bruce Fields <bfields@fieldses.org>
Date: Mar 29, 2007, 21:46 UTC
Message-ID: <20070329214654.GI6143@fieldses.org>
In-Reply-To: <7vabxv3fnx.fsf@assigned-by-dhcp.cox.net>

On Thu, Mar 29, 2007 at 02:26:10PM -0700, Junio C Hamano wrote:

Show 20 quoted lines

> "J. Bruce Fields" <bfields@fieldses.org> writes:
> 
> > On Thu, Mar 29, 2007 at 10:50:51PM +0200, Guennadi Liakhovetski wrote:
> >> Now, my copy of Linus' tree was ATM 1.5GiB big...  Slowly it's getting
> >> scary.
> >
> > On my laptop:
> >
> > [bfields@pad linux]$ du -hs .
> > 1.5G    .
> > [bfields@pad linux]$ du -hs .git
> > 334M    .git
> >
> > So it's mostly the checked out working directory and build
> > stuff.
> >
> > If you really need a ton of build trees then you might just want to do
> > cp -al or something.
> 
> How about suggesting "clone -l -s"?

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.

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

--b.