All of lore.kernel.org
 help / color / mirror / Atom feed
From: "J. Bruce Fields" <bfields@fieldses.org>
To: Junio C Hamano <junkio@cox.net>
Cc: Guennadi Liakhovetski <g.liakhovetski@gmx.de>, git@vger.kernel.org
Subject: Re: basics... when reading docs doesn't help
Date: Thu, 29 Mar 2007 17:46:54 -0400	[thread overview]
Message-ID: <20070329214654.GI6143@fieldses.org> (raw)
In-Reply-To: <7vabxv3fnx.fsf@assigned-by-dhcp.cox.net>

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

  reply	other threads:[~2007-03-29 21:47 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-03-29 20:50 basics... when reading docs doesn't help Guennadi Liakhovetski
2007-03-29 21:16 ` J. Bruce Fields
2007-03-29 21:26   ` Junio C Hamano
2007-03-29 21:46     ` J. Bruce Fields [this message]
2007-03-29 22:13       ` Guennadi Liakhovetski
2007-03-29 22:35         ` Linus Torvalds
2007-03-30 18:16           ` Guennadi Liakhovetski
2007-03-30 18:48             ` Linus Torvalds
2007-03-30 19:49               ` Guennadi Liakhovetski
2007-03-30 20:06                 ` Linus Torvalds
2007-03-30 20:23                 ` Theodore Tso
2007-03-30 20:39                 ` Junio C Hamano
2007-03-30 21:11                   ` Guennadi Liakhovetski
2007-03-30  2:43         ` Theodore Tso
2007-03-30 14:49           ` J. Bruce Fields
2007-03-30 18:02         ` Andreas Herrmann
2007-03-30 18:24           ` Guennadi Liakhovetski
2007-03-29 22:27   ` Matthieu Moy

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20070329214654.GI6143@fieldses.org \
    --to=bfields@fieldses.org \
    --cc=g.liakhovetski@gmx.de \
    --cc=git@vger.kernel.org \
    --cc=junkio@cox.net \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.