From: Andreas Schwab <schwab@linux-m68k.org>
To: Hin-Tak Leung <hintak.leung@gmail.com>
Cc: Nicolas Pitre <nico@cam.org>, git@vger.kernel.org
Subject: Re: git gc expanding packed data?
Date: Sat, 08 Aug 2009 15:25:27 +0200 [thread overview]
Message-ID: <m21vnm8mk8.fsf@igel.home> (raw)
In-Reply-To: <3ace41890908080605k4ec6661bmcb4c87e10bc5fd87@mail.gmail.com> (Hin-Tak Leung's message of "Sat, 8 Aug 2009 14:05:22 +0100")
Hin-Tak Leung <hintak.leung@gmail.com> writes:
> Thanks... It is a difference between svn and git mentality probably -
It is just that the remote is a git-svn tree, with only a few branches
created as local branches.
> The case with gcc is probably quite extreme - many user branches, and
> very large code base - but is there anything on the git side with git
> gc which can lessen this kind of pathological behavior (expanding
> packs)?
If you fetch all refs, not only refs/heads/*, all objects will be
referenced.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2009-08-08 13:25 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-08 1:11 git gc expanding packed data? Andreas Schwab
2009-08-08 13:05 ` Hin-Tak Leung
2009-08-08 13:25 ` Andreas Schwab [this message]
2009-08-09 2:56 ` Nicolas Pitre
2009-08-09 7:43 ` Andreas Schwab
2009-09-25 18:05 ` git clone sending unneeded objects (was : git gc expanding packed data?) Jason Merrill
2009-09-25 19:34 ` git clone sending unneeded objects Matthieu Moy
2009-09-25 19:43 ` Jason Merrill
2009-09-25 19:53 ` Nicolas Pitre
2009-09-25 20:20 ` Jason Merrill
2009-09-25 20:47 ` Nicolas Pitre
2009-09-25 23:17 ` Jason Merrill
2009-09-26 0:49 ` Nicolas Pitre
2009-09-26 3:54 ` [PATCH] make 'git clone' ask the remote only for objects it cares about Nicolas Pitre
2009-09-26 7:21 ` Andreas Schwab
2009-09-26 19:50 ` Shawn O. Pearce
2009-09-27 0:26 ` Nicolas Pitre
2009-09-26 4:44 ` git clone sending unneeded objects Jason Merrill
2009-09-26 13:33 ` Jason Merrill
2009-09-27 2:26 ` Nicolas Pitre
2009-09-27 1:27 ` Nicolas Pitre
2009-09-27 2:04 ` Shawn O. Pearce
2009-09-27 2:31 ` Nicolas Pitre
2009-09-27 4:35 ` Jason Merrill
2009-09-28 4:18 ` Nicolas Pitre
2009-09-26 0:43 ` Hin-Tak Leung
-- strict thread matches above, loose matches on Subject: below --
2009-08-04 20:25 git gc expanding packed data? Hin-Tak Leung
2009-08-05 22:39 ` Nicolas Pitre
2009-08-11 10:17 ` Hin-Tak Leung
2009-08-11 21:33 ` Nicolas Pitre
2009-08-12 14:45 ` Hin-Tak Leung
2009-08-12 15:35 ` Nicolas Pitre
2009-08-13 17:31 ` Hin-Tak Leung
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=m21vnm8mk8.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=hintak.leung@gmail.com \
--cc=nico@cam.org \
/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.