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

Re: Should object repacking only update server-info for packs instead of doing it for refs?

From
Taylor Blau <me@ttaylorr.com>
Date
Oct 14, 2024, 21:25 UTC
Message-ID
<Zw2MVqi0FLcMuR8Z@nand.local>
In-Reply-To
<569E3AEA-AC68-4186-B38C-2E47DAB9890E@gmail.com>
On Mon, Oct 14, 2024 at 09:33:17PM +0100, Luca Milanesio wrote:
Show 5 quoted lines
> > It seems counterintuitive that an operation designed to repack
> > objects would be performing maintenance of any sort on refs?
>
> True, it should not touch info/refs IMHO, as you’re really not
> changing any refs.

Right. I don't think that the current behavior is a bug, but just that it's doing unnecessary work from within 'git repack' to update the info/refs file when it's known ahead of time that the refs haven't changed.

I think it's reasonable to skip this step when repacking, but of course we would still want to update info/packs (assuming that the repack wasn't a noop, of course).

Thanks, Taylor

Previous: Luca MilanesioNext: Patrick Steinhardt
Message 3 of 7 in “Should object repacking only update server-info for packs instead of doing it for refs?”
  1. Martin FickOct 14, 2024
  2. Luca MilanesioOct 14, 2024
  3. Taylor BlauOct 14, 2024
  4. Patrick SteinhardtOct 15, 2024
  5. Luca MilanesioOct 15, 2024
  6. Patrick SteinhardtOct 15, 2024
  7. Taylor BlauOct 15, 2024

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.