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

Re: [RFC/PATCH] Add a --nosort option to pack-objects

From
Mike Hommey <mh@glandium.org>
Date
Dec 7, 2007, 21:44 UTC
Message-ID
<20071207214426.GA13170@glandium.org>
In-Reply-To
<alpine.LFD.0.99999.0712071622150.555@xanadu.home>
On Fri, Dec 07, 2007 at 04:24:17PM -0500, Nicolas Pitre wrote:
Show 9 quoted lines
> On Fri, 7 Dec 2007, Mike Hommey wrote:
> 
> > While most of the time the heuristics used by pack-objects to sort the
> > given object list are satisfying enough, there are cases where it can be
> > useful for the user to sort the list with heuristics that would be better
> > suited.
> 
> Could you please elaborate on those cases where the current heuristic 
> would be unsatisfactory?

I imagine it could be useful when importing a huge tree in the first commit, when some data in the tree is redundant with (or similar to) others in the same tree. I guess there could be some other VCS use-cases.

The real case where I've been using this is that I use git to store my debian build logs in an efficient manner, and having a custom-sorted list of objects ends up being much faster and less memory consuming than using a huge window (and 1GB of logs became less than 10MB).

Mike
Previous: Nicolas PitreNext: Junio C Hamano
Message 3 of 8 in “Add a --nosort option to pack-objects”
  1. Add a --nosort option to pack-objectsMike Hommey, Dec 7, 2007
  2. Nicolas PitreDec 7, 2007
  3. Mike HommeyDec 7, 2007
  4. Junio C HamanoDec 7, 2007
  5. Junio C HamanoDec 7, 2007
  6. Mike HommeyDec 7, 2007
  7. Nicolas PitreDec 7, 2007
  8. Mike HommeyDec 8, 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.