git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: [PATCH 2/2] Teach receive-pack how to keep pack files based on object count.

From
Shawn Pearce <spearce@spearce.org>
Date
Oct 31, 2006, 20:11 UTC
Message-ID
<20061031201148.GD23671@spearce.org>
In-Reply-To
<Pine.LNX.4.64.0610311447250.11384@xanadu.home>
Nicolas Pitre <nico@cam.org> wrote:
Show 21 quoted lines
> 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).

Its next on my list of things to do. Hopefully I'll be able to implement it today.

I'm thinking of just brute forcing it: put enough identifying data into the .keep file to make it unique, then go through every local pack and look at their .keep file; if the content matches what receive-pack asked index-pack to put there then remove it.

Previous: Nicolas PitreNext: Nicolas Pitre
Message 3 of 7 in “Teach receive-pack how to keep pack files based on object count.”
  1. 2/2 Teach receive-pack how to keep pack files based on object count.Shawn Pearce, Oct 31, 2006
  2. Nicolas PitreOct 31, 2006
  3. Shawn PearceOct 31, 2006
  4. Nicolas PitreOct 31, 2006
  5. Shawn PearceOct 31, 2006
  6. Nicolas PitreOct 31, 2006
  7. Junio C HamanoOct 31, 2006

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.