public inbox for git@vger.kernel.org 
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail•com>
To: Junio C Hamano <gitster@pobox•com>, Elijah Newren <newren@gmail•com>
Cc: git@vger•kernel.org, Ayush Chandekar <ayu.chandekar@gmail•com>
Subject: Re: What's cooking in git.git (Aug 2025, #10; Fri, 22)
Date: Tue, 26 Aug 2025 12:37:03 -0400	[thread overview]
Message-ID: <c3c0fbef-f395-4972-8352-dd89af6799d5@gmail.com> (raw)
In-Reply-To: <xmqqbjo2kqz8.fsf@gitster.g>

On 8/26/2025 12:06 PM, Junio C Hamano wrote:
> Elijah Newren <newren@gmail•com> writes:
> 
>>>  Needs to wait for the base topic to solidify.
>>>  source: <pull.1941.v2.git.1752716054.gitgitgadget@gmail•com>
>>
>> Maybe also mark as expecting a reroll?  (cf.
>> CABPp-BFzMLGJwz4QqYtvw3zRYgmC=Mb8T8GCOsrLZqT2z+8H7A@mail•gmail.com and
>> CABPp-BHLcy-A4yLR8gP1Sjt_EKQ4K08kPyb7G6yifdZj+0MJNg@mail•gmail.com)
> 
> Good idea.
> 
> As these are primarily to remind me, I'd prefer to point at articles
> from the topic author that said "in the next reroll I'll do this"
> rather than articles from reviewers when leaving a note to explain
> why I do *not* want to merge it yet.  But this second round does
> look like it needs responses to reviews.

Yes, it does need responses to reviews. And I'm looking forward
to the base topic getting a reroll before spending too much time
on a new version.

I'd consider this one blocked at the moment. I reached out to
Ayush earlier to see about progress there.

Thanks,
-Stolee


      reply	other threads:[~2025-08-26 16:37 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-08-23  0:10 What's cooking in git.git (Aug 2025, #10; Fri, 22) Junio C Hamano
2025-08-26 13:40 ` Phillip Wood
2025-08-26 15:04 ` Elijah Newren
2025-08-26 16:06   ` Junio C Hamano
2025-08-26 16:37     ` Derrick Stolee [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

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

  git send-email \
    --in-reply-to=c3c0fbef-f395-4972-8352-dd89af6799d5@gmail.com \
    --to=stolee@gmail$(echo .)com \
    --cc=ayu.chandekar@gmail$(echo .)com \
    --cc=git@vger$(echo .)kernel.org \
    --cc=gitster@pobox$(echo .)com \
    --cc=newren@gmail$(echo .)com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox