git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: ds/maintenance-part-1 (was Re: What's cooking in git.git (Sep 2020, #04; Wed, 16))
Date: Thu, 17 Sep 2020 13:37:30 -0400	[thread overview]
Message-ID: <f22e0a5e-3e08-874a-bb86-a3a3be108bbb@gmail.com> (raw)
In-Reply-To: <xmqqo8m4s6mi.fsf@gitster.c.googlers.com>

On 9/17/2020 12:36 PM, Junio C Hamano wrote:
> Derrick Stolee <stolee@gmail.com> writes:
> 
>> This message [1] includes a simple forward-fix for the
>> parsing logic. I mention a re-roll in my preface, but
>> I was talking about a potential re-roll of part-3 when
>> that gets more feedback.
>>
>> My hope was that the quick fix could be applied directly
>> on top of this branch and then cook in next as planned.
>> I'll accept a delay if you think that is merited, but "on
>> hold" just seems like you are waiting for something more
>> from me.
> 
> I was expecting [1] to be corrected in the commit in the series
> before it hits 'next', not a "oops we screwed up earlier so here is
> a band-aid on top", which we must do after the topic is already in
> 'next' or 'master', and also hoping that it would happen quickly so
> that we can move it forward.

Noted. I can squash it in and send a new series.

Thanks,
-Stolee

>> [1] https://lore.kernel.org/git/0b35829f-a83b-a093-2dc5-0e7d3b42fd15@gmail.com/

  reply	other threads:[~2020-09-17 17:50 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-17  3:47 What's cooking in git.git (Sep 2020, #04; Wed, 16) Junio C Hamano
2020-09-17 12:54 ` ds/maintenance-part-1 (was Re: What's cooking in git.git (Sep 2020, #04; Wed, 16)) Derrick Stolee
2020-09-17 16:36   ` Junio C Hamano
2020-09-17 17:37     ` Derrick Stolee [this message]
2020-09-17 19:52 ` What's cooking in git.git (Sep 2020, #04; Wed, 16) Junio C Hamano
2020-09-17 21:39 ` Junio C Hamano
2020-09-20 17:02   ` Johannes Schindelin

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=f22e0a5e-3e08-874a-bb86-a3a3be108bbb@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).