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

Re: [PATCH v2] refs: make explicit that ref_iterator_peel returns boolean

From
Junio C Hamano <gitster@pobox.com>
Date
Jul 6, 2021, 19:54 UTC
Message-ID
<xmqqo8bfi5f5.fsf@gitster.g>
In-Reply-To
<CAFQ2z_M-NmN2xVjoudzEqpAvugyRBQkKh+N4r_s_W=U99Uvwpg@mail.gmail.com>
Han-Wen Nienhuys <hanwen@google.com> writes:
Show 15 quoted lines
> On Thu, May 20, 2021 at 11:04 AM Han-Wen Nienhuys <hanwen@google.com> wrote:
>> > So this corresponds to the bottommost step in the series that is
>> > queued as hn/reftable, with the difference at the end of this
>> > message.
>> >
>> > Do you want me to replace that single step with this version and
>> > rebuild the remainder of the topic on top?
>>
>> Yes.
>>
>> I'm hoping this can graduate soon, so the hn/reftable topic becomes
>> smaller (I don't know what that means for your organization of the
>> seen branch).
>
> Any update on this? This wasn't queued for next, but I believe it should be.

Sorry, I thought you meant you wanted to fix up the bottommost commit in that series, which I think was already done at 617480d7 (refs: make explicit that ref_iterator_peel returns boolean, 2021-05-19), and did not realize that you wanted a separate single patch topic for this step, on top of which the remainder of the other topic builds.

Will do.  Thanks.
Previous: Han-Wen Nienhuys
Message 6 of 6 in “refs: ref_iterator_peel returns boolean, rather than peel_status”
  1. refs: ref_iterator_peel returns boolean, rather than peel_statusHan-Wen Nienhuys via GitGitGadget, Apr 15, 2021
  2. refs: make explicit that ref_iterator_peel returns booleanHan-Wen Nienhuys via GitGitGadget, May 19, 2021
  3. Junio C HamanoMay 19, 2021
  4. Han-Wen NienhuysMay 20, 2021
  5. Han-Wen NienhuysJul 6, 2021
  6. Junio C HamanoJul 6, 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.