git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: A summary of in-flight topics
Date: Wed, 25 Jan 2023 09:12:39 -0800	[thread overview]
Message-ID: <xmqqzga6edx4.fsf@gitster.g> (raw)
In-Reply-To: <CABPp-BH0LwHvN_bXp0BpekQ+f+15KNXQRzf5LCn3_BhcPzB-3A@mail.gmail.com> (Elijah Newren's message of "Wed, 25 Jan 2023 08:05:57 -0800")

Elijah Newren <newren@gmail.com> writes:

> On Tue, Jan 24, 2023 at 2:37 PM Junio C Hamano <gitster@pobox.com> wrote:
> [...]
>>  - ab/sequencer-unleak                                          01-18          #8
>
> Perhaps move to "Expecting a hopefully minor and final reroll"?  See
> e.g. https://lore.kernel.org/git/xmqqedry17r4.fsf@gitster.g/ where you
> commented on Phillip's approving the code changes but wanting a number
> of commit message cleanups and fixes.  Ævar did send a v3, and Phillip
> commented on two of those patches, suggesting one could still use some
> commit message cleanups.

Thanks, you're right.

>>  - ab/various-leak-fixes                                        01-18         #19
>
> Isn't this already merged as 9ea1378d04 ("Merge branch
> 'ab/various-leak-fixes'", 2022-12-14)?

The cover letter of its first iteration says

    This is a follow-up to the ab/various-leak-fixes topic merged in
    9ea1378d046 (Merge branch 'ab/various-leak-fixes', 2022-12-14). Like
    that topic this is mixed collection of various leak fixes, all of
    which should be simple to review & reason about.

Unfortunately the text does not appear in the cover for the
latest iteration, but that is how the topic name was reused.

THanks.

      reply	other threads:[~2023-01-25 17:13 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-01-24 22:30 A summary of in-flight topics Junio C Hamano
2023-01-25 16:05 ` Elijah Newren
2023-01-25 17:12   ` 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:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: http://vger.kernel.org/majordomo-info.html

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

  git send-email \
    --in-reply-to=xmqqzga6edx4.fsf@gitster.g \
    --to=gitster@pobox.com \
    --cc=git@vger.kernel.org \
    --cc=newren@gmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* 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 public inbox

	https://80x24.org/mirrors/git.git

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).