From: Nicolas Pitre <nico@cam.org>
To: Shawn Pearce <spearce@spearce.org>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 2/2] Teach receive-pack how to keep pack files based on object count.
Date: Tue, 31 Oct 2006 14:56:50 -0500 (EST) [thread overview]
Message-ID: <Pine.LNX.4.64.0610311447250.11384@xanadu.home> (raw)
In-Reply-To: <20061031075704.GB7691@spearce.org>
On Tue, 31 Oct 2006, Shawn Pearce wrote:
> Since keeping a pushed pack or exploding it into loose objects
> should be a local repository decision this teaches receive-pack
> to decide if it should call unpack-objects or index-pack --stdin
> --fix-thin based on the setting of receive.unpackLimit and the
> number of objects contained in the received pack.
This works fine when used with my replacement patch for your [1/2] one.
> Currently this leaves every received pack as a kept pack. We really
> don't want that as received packs will tend to be small. Instead we
> want to delete the .keep file automatically after all refs have
> been updated. That is being left as room for future improvement.
I think this should be solved before rx packs are actually stored as
packs though. Otherwise people will end up with unwanted .keep files
left around. Maybe having a much bigger default for object number
treshold for the time being? (unless this patch is applied to "next" at
the same time as another one that actually deals with those .keep
files).
next prev parent reply other threads:[~2006-10-31 19:56 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-31 7:57 [PATCH 2/2] Teach receive-pack how to keep pack files based on object count Shawn Pearce
2006-10-31 19:56 ` Nicolas Pitre [this message]
2006-10-31 20:11 ` Shawn Pearce
2006-10-31 21:08 ` Nicolas Pitre
2006-10-31 21:29 ` Shawn Pearce
2006-10-31 22:06 ` Nicolas Pitre
2006-10-31 22:27 ` Junio C Hamano
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=Pine.LNX.4.64.0610311447250.11384@xanadu.home \
--to=nico@cam.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=spearce@spearce.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).