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

Re: [PATCH v2 1/1] builtin/pack-objects.c: avoid iterating all refs

From
Jacob Vosmaer <jacob@gitlab.com>
Date
Jan 20, 2021, 21:46 UTC
Message-ID
<CADMWQoPrKBjLM5ABhhhCibEyJVOXQxsNkncSU6dmwjynQ1oCcQ@mail.gmail.com>
In-Reply-To
<YAiIbEAZSlL7B+am@coredump.intra.peff.net>
On Wed, Jan 20, 2021 at 8:45 PM Jeff King <peff@peff.net> wrote:
> I also rage-replaced peel_ref() with a function taking an oid so we
> never have to do that digging again. Posted separately in its own
> thread.

That sounds like a good solution. Where does that leave my patch? Do I need to wait for that new commit somehow? I don't know how that works, "contributing to Git" wise.

Previous: Jeff KingNext: Taylor Blau
Message 8 of 11 in “builtin/pack-objects.c: avoid iterating all refs”
  1. 0/1 builtin/pack-objects.c: avoid iterating all refsJacob Vosmaer, Jan 20, 2021
  2. 1/1 builtin/pack-objects.c: avoid iterating all refsJacob Vosmaer, Jan 20, 2021
  3. Taylor BlauJan 20, 2021
  4. Jeff KingJan 20, 2021
  5. Taylor BlauJan 20, 2021
  6. Jacob VosmaerJan 20, 2021
  7. Jeff KingJan 20, 2021
  8. Jacob VosmaerJan 20, 2021
  9. Taylor BlauJan 20, 2021
  10. Jeff KingJan 21, 2021
  11. Jacob VosmaerJan 22, 2021

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.