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

Re: Why does send-pack call pack-objects for all remote refs?

From
Jeff King <peff@peff.net>
Date
Dec 7, 2015, 22:57 UTC
Message-ID
<20151207225714.GA3785@sigill.intra.peff.net>
In-Reply-To
<xmqqvb89lw5f.fsf@gitster.mtv.corp.google.com>
On Mon, Dec 07, 2015 at 02:41:00PM -0800, Junio C Hamano wrote:
Show 6 quoted lines
> Also it was unclear if you are working with a shallow repository.
> The performance trade-off made between the packsize and the cycles
> is somewhat different between a normal and a shallow repository,
> e.g. 2dacf26d (pack-objects: use --objects-edge-aggressive for
> shallow repos, 2014-12-24) might be a good starting point to think
> about this issue.

Also note that for a while the "aggressive" form was used everywhere. I think that started in fbd4a70 (list-objects: mark more commits as edges in mark_edges_uninteresting - 2013-08-16), and was fixed in 1684c1b (rev-list: add an option to mark fewer edges as uninteresting, 2014-12-24).

So it was present from v1.8.4.2 up to v2.3.0.
-Peff
Previous: Junio C HamanoNext: Daniel Koverman
Message 3 of 10 in “Why does send-pack call pack-objects for all remote refs?”
  1. Daniel KovermanDec 7, 2015
  2. Junio C HamanoDec 7, 2015
  3. Jeff KingDec 7, 2015
  4. Daniel KovermanDec 8, 2015
  5. Jeff KingDec 10, 2015
  6. Nasser GrainawiDec 12, 2015
  7. Daniel KovermanDec 14, 2015
  8. Jeff KingDec 14, 2015
  9. Jonathan NiederDec 14, 2015
  10. Jeff KingDec 14, 2015

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.