list mirror (unofficial, one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <>
To: Han-Wen Nienhuys <>
Cc: Han-Wen Nienhuys via GitGitGadget <>,
	git <>, Han-Wen Nienhuys <>
Subject: Re: [PATCH v2] refs: make explicit that ref_iterator_peel returns boolean
Date: Tue, 06 Jul 2021 12:54:54 -0700	[thread overview]
Message-ID: <xmqqo8bfi5f5.fsf@gitster.g> (raw)
In-Reply-To: <> (Han-Wen Nienhuys's message of "Tue, 6 Jul 2021 20:09:40 +0200")

Han-Wen Nienhuys <> writes:

> On Thu, May 20, 2021 at 11:04 AM Han-Wen Nienhuys <> 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.

      reply	other threads:[~2021-07-06 19:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15 11:02 [PATCH] refs: ref_iterator_peel returns boolean, rather than peel_status Han-Wen Nienhuys via GitGitGadget
2021-05-19 15:31 ` [PATCH v2] refs: make explicit that ref_iterator_peel returns boolean Han-Wen Nienhuys via GitGitGadget
2021-05-19 22:58   ` Junio C Hamano
2021-05-20  9:04     ` Han-Wen Nienhuys
2021-07-06 18:09       ` Han-Wen Nienhuys
2021-07-06 19:54         ` Junio C Hamano [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:

  List information:

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=xmqqo8bfi5f5.fsf@gitster.g \ \ \ \ \ \

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this inbox:

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).