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

Re: [PATCH 0/2] Avoid rewriting "packed-refs" unnecessarily

From
Eric Sunshine <sunshine@sunshineco.com>
Date
Oct 25, 2017, 20:10 UTC
Message-ID
<CAPig+cSrjiyGUm0n5dvowjNYZMSGvb+SZJ=haTsxXi9NcThA7A@mail.gmail.com>
In-Reply-To
<cover.1508924577.git.mhagger@alum.mit.edu>
On Wed, Oct 25, 2017 at 5:53 AM, Michael Haggerty <mhagger@alum.mit.edu> wrote:
Show 10 quoted lines
> Since commit dc39e09942 (files_ref_store: use a transaction to update
> packed refs, 2017-09-08), we've been rewriting the `packed-refs` file
> unnecessarily when deleting a loose reference that has no packed
> counterpart. Add some tests demonstrating this problem, then fix it by
> teaching `files_backend` to see whether any references being deleted
> have packed versions, and if not, skipping the packed_refs
> transaction.
>
> This is a mild regression since 2.14, which avoided rewriting the
> `packed-refs` file in these cases [...]

Should the above information (that this fixes a regression) be mentioned in the commit message of at least one of the patches (probably 2/2)? Without such context, it may not be clear to someone later reading those commit message -- someone who wasn't following this email discussion -- that this behavior had been lost and is now being restored.

Previous: Michael HaggertyNext: Michael Haggerty
Message 6 of 7 in “Avoid rewriting "packed-refs" unnecessarily”
  1. 0/2 Avoid rewriting "packed-refs" unnecessarilyMichael Haggerty, Oct 25, 2017
  2. 2/2 files-backend: don't rewrite the `packed-refs` file unnecessarilyMichael Haggerty, Oct 25, 2017
  3. Junio C HamanoOct 26, 2017
  4. Michael HaggertyOct 26, 2017
  5. 1/2 t1409: check that `packed-refs` is not rewritten unnecessarilyMichael Haggerty, Oct 25, 2017
  6. Eric SunshineOct 25, 2017
  7. Michael HaggertyOct 28, 2017

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.