From: Adam Heath <doogie@brainfood•com>
To: Nicolas Pitre <nico@cam•org>
Cc: Sam Hocevar <sam@zoy•org>, git@vger•kernel.org
Subject: Re: large(25G) repository in git
Date: Tue, 24 Mar 2009 19:57:46 -0500 [thread overview]
Message-ID: <49C9818A.9040507@brainfood.com> (raw)
In-Reply-To: <alpine.LFD.2.00.0903242025110.26337@xanadu.home>
Nicolas Pitre wrote:
> On Tue, 24 Mar 2009, Adam Heath wrote:
>
>> Sam Hocevar wrote:
>>> In your particular case, I would suggest setting pack.packSizeLimit
>>> to something lower. This would reduce the time spent generating a new
>>> pack file if the problem were to happen again.
>> Yeah, saw that one, but *after* I had this problem. The default, if
>> not set, is unlimited, which in this case, is definately *not* what we
>> want.
>
> In your particular case, if the problem is actually what I think it is,
> the pack.packSizeLimit wouldn't have made any difference. This setting
> affects local repacking only and has no effect what so ever on the push
> operation.
Ooh. Care to enlighten those of us not blessed with git internal
knowledge?
On another note, anyone have a goat I can buy, for the sacrifice?
next prev parent reply other threads:[~2009-03-25 1:00 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-23 21:10 large(25G) repository in git Adam Heath
2009-03-24 1:19 ` Nicolas Pitre
2009-03-24 17:59 ` Adam Heath
2009-03-24 18:31 ` Nicolas Pitre
2009-03-24 20:55 ` Adam Heath
2009-03-25 1:21 ` Nicolas Pitre
2009-03-24 18:33 ` david
2009-03-24 8:59 ` Andreas Ericsson
2009-03-24 22:35 ` Adam Heath
2009-03-24 21:04 ` Sam Hocevar
2009-03-24 21:44 ` Adam Heath
2009-03-25 0:28 ` Nicolas Pitre
2009-03-25 0:57 ` Adam Heath [this message]
2009-03-25 1:47 ` Nicolas Pitre
2009-03-26 15:43 ` Marcel M. Cary
2009-03-26 16:35 ` Adam Heath
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=49C9818A.9040507@brainfood.com \
--to=doogie@brainfood$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=nico@cam$(echo .)org \
--cc=sam@zoy$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox