git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Derrick Stolee <stolee@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "SZEDER Gábor" <szeder.dev@gmail.com>,
	"Phillip Wood" <phillip.wood123@gmail.com>,
	git@vger.kernel.org
Subject: Re: What's cooking in git.git (Nov 2019, #03; Tue, 19)
Date: Thu, 21 Nov 2019 06:10:55 -0500	[thread overview]
Message-ID: <dc0bbc13-8204-c6b4-8d3b-db101027fe1c@gmail.com> (raw)
In-Reply-To: <xmqqy2wa9ibs.fsf@gitster-ct.c.googlers.com>

On 11/20/2019 7:36 PM, Junio C Hamano wrote:
> Derrick Stolee <stolee@gmail.com> writes:
> 
>>> OK.  I had an impression that it was something relatively easily
>>> patched to restore the plumbing behaviour without taking the
>>> remainder of the series with a follow-on work.  If it is not the
>>> case, perhaps I should revert the merge to 'next' and kick it back
>>> to 'pu'.
>>>
>>> Thanks for stopping me.
>>
>> That commit can be ejected from the series without affecting the
>> correctness of any of the other commits. That will require reverting
>> the merge at this point, though.
> 
> I've done the "reverting" part of everything, so that other patches
> that need further work, if any, can be given a fresh start.

I see that more feedback was given, so I'm working on a new version.

Thanks,
-Stolee


  reply	other threads:[~2019-11-21 11:11 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-11-19  7:05 What's cooking in git.git (Nov 2019, #03; Tue, 19) Junio C Hamano
2019-11-19  9:38 ` Danh Doan
2019-11-20  2:52   ` Junio C Hamano
2019-11-19 17:58 ` SZEDER Gábor
2019-11-20  3:02   ` Junio C Hamano
2019-11-20 13:58     ` Derrick Stolee
2019-11-21  0:36       ` Junio C Hamano
2019-11-21 11:10         ` Derrick Stolee [this message]
2019-11-22  5:42           ` Junio C Hamano
2019-11-19 18:01 ` ag/sequencer-todo-updates , was " Alban Gruin
2019-11-19 20:41   ` Jonathan Tan
2019-11-20  3:03     ` Junio C Hamano
2019-11-21  8:17       ` Alban Gruin
2019-11-23  0:47     ` Alban Gruin
2019-11-20 23:32 ` Denton Liu
2019-11-21  0:39   ` Junio C Hamano
2019-11-23 20:35 ` Philippe Blain

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=dc0bbc13-8204-c6b4-8d3b-db101027fe1c@gmail.com \
    --to=stolee@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=phillip.wood123@gmail.com \
    --cc=szeder.dev@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.
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 NNTP newsgroup(s).