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

Re: [PATCH] Split packs from git-repack should have descending timestamps

From
Shawn O. Pearce <spearce@spearce.org>
Date
May 25, 2007, 00:46 UTC
Message-ID
<20070525004610.GP28023@spearce.org>
In-Reply-To
<465612CE.4080605@gmail.com>
Dana How <danahow@gmail.com> wrote:
Show 12 quoted lines
> 
> If git-repack produces multiple split packs because
> --max-pack-size was in effect,  the first pack written
> should have the latest timestamp because:
> (1) sha1_file.c:rearrange_packed_git() puts more recent
>     pack files at the beginning of the search list;  and
> (2) the most recent objects are written out first
>     while packing.
> 
> This is based on next rather than master to avoid merge
> conflicts with changes already in git-repack.sh due to
> the --max-pack-size patchset.

Ack. Given our mtime based sorting routine, even without your recent patch to improve it, I think we definately want this type of behavior built into git-repack.sh. Good follow-on to your --max-pack-size series.

-- 
Shawn.
Previous: Dana HowNext: Junio C Hamano
Message 2 of 5 in “Split packs from git-repack should have descending timestamps”
  1. Split packs from git-repack should have descending timestampsDana How, May 24, 2007
  2. Shawn O. PearceMay 25, 2007
  3. Junio C HamanoMay 25, 2007
  4. Dana HowMay 25, 2007
  5. Junio C HamanoMay 25, 2007

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.