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

Re: [PATCH] refs: speed up is_refname_available

From
Jeff King <peff@peff.net>
Date
Sep 11, 2014, 18:31 UTC
Message-ID
<20140911183143.GB18382@peff.net>
In-Reply-To
<xmqqy4tqdr1r.fsf@gitster.dls.corp.google.com>
On Thu, Sep 11, 2014 at 10:07:28AM -0700, Junio C Hamano wrote:
Show 10 quoted lines
> Jeff King <peff@peff.net> writes:
> 
> > This has a fairly straightforward conflict with the ref-transaction
> > stuff in pu. The "oldrefname" parameter to is_refname_available became a
> > list of items;
> 
> Hmph, the trouble I had while reading the conflicts was about the
> new "we skip these when repacking", not "oldrefname".
> 
> Will check your suggested resolution later today.  Thanks.

I didn't see any conflict related to repacking. If I am reading 54e696fc433 correctly, the single "oldrefname" became a list "skip" in the name_conflict_* code. My series dropped name_conflict_*, but gave a similar adaptation to the replacement.

The "skip while repacking" code is repack_without_refs, but I don't think I touched anything that conflicted there.

-Peff
Previous: Junio C Hamano
Message 7 of 7 in “refs: speed up is_refname_available”
  1. refs: speed up is_refname_availableJeff King, Sep 10, 2014
  2. refs: speed up is_refname_availableJeff King, Sep 10, 2014
  3. Junio C HamanoSep 10, 2014
  4. Jeff KingSep 11, 2014
  5. Junio C HamanoSep 10, 2014
  6. Junio C HamanoSep 11, 2014
  7. Jeff KingSep 11, 2014

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.