From: Junio C Hamano <gitster@pobox.com>
To: Elijah Newren <newren@gmail.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Feb 2020, #04; Mon, 17)
Date: Sat, 22 Feb 2020 09:18:22 -0800 [thread overview]
Message-ID: <xmqq36b27d7l.fsf@gitster-ct.c.googlers.com> (raw)
In-Reply-To: <CABPp-BEnt4C_7XyxQKxk4aga=JjM9fXCE-7SFp7azO_v5-pQYw@mail.gmail.com> (Elijah Newren's message of "Fri, 21 Feb 2020 19:11:05 -0800")
Elijah Newren <newren@gmail.com> writes:
>> > * en/rebase-backend (2020-02-16) 20 commits
>> > - rebase: rename the two primary rebase backends
>> >...
>> > - t3404: directly test the behavior of interest
>> > - git-rebase.txt: update description of --allow-empty-message
>> >
>> > "git rebase" has learned to use the sequencer backend by default,
>> > while allowing "--am" option to go back to the traditional "am"
>> > backend.
>> >
>> > The last step may be rushing things a bit and may want to be
>> > taken separately.
>> > cf. <pull.679.v5.git.git.1581802602.gitgitgadget@gmail.com>
>
> In contrast, this whole series I think is complete and ready to merge
> down. Both Phillip and Dscho have commented that they agree with the
> direction of the final patch, Phillip has reviewed multiple rounds and
> sounds happy with it, and most of this series already spent some time
> in 'next' during the 2.25 cycle.
Let's merge it down then. Thanks.
next prev parent reply other threads:[~2020-02-22 17:18 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-17 22:08 What's cooking in git.git (Feb 2020, #04; Mon, 17) Junio C Hamano
2020-02-18 3:30 ` Elijah Newren
2020-02-18 16:00 ` en/rebase-backend, was " Johannes Schindelin
2020-02-26 10:34 ` Alban Gruin
2020-02-22 3:11 ` Elijah Newren
2020-02-22 17:18 ` Junio C Hamano [this message]
2020-02-19 19:58 ` Taylor Blau
2020-02-19 20:50 ` Eric Sunshine
2020-02-19 21:51 ` Junio C Hamano
2020-02-19 22:07 ` Taylor Blau
2020-02-21 16:26 ` Phillip Wood
2020-02-22 3:03 ` Elijah Newren
2020-02-22 17:16 ` Junio C Hamano
2020-02-26 20:04 ` Elijah Newren
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=xmqq36b27d7l.fsf@gitster-ct.c.googlers.com \
--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.
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).