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

Re: [PATCH v2] builtin/repack.c: avoid making cruft packs preferred

From
Patrick Steinhardt <ps@pks.im>
Date
Oct 5, 2023, 11:14 UTC
Message-ID
<ZR6ajQa8bh5HKsnr@tanuki>
In-Reply-To
<035393935108d02aaf8927189b05102f4f74f340.1696370003.git.me@ttaylorr.com>

On Tue, Oct 03, 2023 at 05:54:19PM -0400, Taylor Blau wrote: [snip]

Show 8 quoted lines
> @@ -801,6 +814,38 @@ static int write_midx_included_packs(struct string_list *include,
>  	if (preferred)
>  		strvec_pushf(&cmd.args, "--preferred-pack=%s",
>  			     pack_basename(preferred));
> +	else if (names->nr) {
> +		/* The largest pack was repacked, meaning that either
> +		 * one or two packs exist depending on whether the
> +		 * repository has a cruft pack or not.
Nit: this comment will grow stale soonish once your patch series lands
that introduces a maximum packfile size for cruft packs as there can be
arbitrarily many cruft packs from thereon.
Show 8 quoted lines
> +		 * Select the non-cruft one as preferred to encourage
> +		 * pack-reuse among packs containing reachable objects
> +		 * over unreachable ones.
> +		 *
> +		 * (Note we could write multiple packs here if
> +		 * `--max-pack-size` was given, but any one of them
> +		 * will suffice, so pick the first one.)
> +		 */
Well, okay, you kind of acknowledge this here.

The rest of this patch series looks good to me and makes sense. I don't really think that this comment here is worth a reroll.

Patrick
Previous: Jeff KingNext: Eric Sunshine
Message 9 of 10 in “builtin/repack.c: avoid making cruft packs preferred”
  1. builtin/repack.c: avoid making cruft packs preferredTaylor Blau, Oct 3, 2023
  2. Taylor BlauOct 3, 2023
  3. Junio C HamanoOct 3, 2023
  4. Taylor BlauOct 3, 2023
  5. Jeff KingOct 3, 2023
  6. Taylor BlauOct 3, 2023
  7. builtin/repack.c: avoid making cruft packs preferredTaylor Blau, Oct 3, 2023
  8. Jeff KingOct 4, 2023
  9. Patrick SteinhardtOct 5, 2023
  10. Eric SunshineOct 5, 2023

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.