From: Phillip Wood <phillip.wood123@gmail.com>
To: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Cc: Elijah Newren <newren@gmail.com>,
Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: What's cooking in git.git (Feb 2020, #04; Mon, 17)
Date: Fri, 21 Feb 2020 16:26:18 +0000 [thread overview]
Message-ID: <e9984c53-7266-c438-87f5-7f5474e3adce@gmail.com> (raw)
In-Reply-To: <xmqq36b8lvdl.fsf@gitster-ct.c.googlers.com>
On 17/02/2020 22:08, Junio C Hamano wrote:
> Here are the topics that have been cooking. Commits prefixed with
> '-' are only in 'pu' (proposed updates) while commits prefixed with
> '+' are in 'next'. The ones marked with '.' do not appear in any of
> the integration branches, but I am still holding onto them.
>
> Accumulated fixes on the 'master' front have been flushed to 'maint'
> and a new maintenance release 2.25.1 has been tagged.
> [...]
> [Stalled]
>
> * pw/advise-rebase-skip (2019-12-06) 9 commits
> - rebase -i: leave CHERRY_PICK_HEAD when there are conflicts
> - rebase: fix advice when a fixup creates an empty commit
> - commit: give correct advice for empty commit during a rebase
> - commit: encapsulate determine_whence() for sequencer
> - commit: use enum value for multiple cherry-picks
> - sequencer: write CHERRY_PICK_HEAD for reword and edit
> - cherry-pick: check commit error messages
> - cherry-pick: add test for `--skip` advice in `git commit`
> - t3404: use test_cmp_rev
>
> The mechanism to prevent "git commit" from making an empty commit
> or amending during an interrupted cherry-pick was broken during the
> rewrite of "git rebase" in C, which has been corrected.
>
> What's the status of this one?
> The tip two are still RFC.
The tip "rebase -i: leave CHERRY_PICK_HEAD when there are conflicts"
needs reworking and can be dropped (cf
<7e1b92f5-48df-e202-ebcc-5b15987a7d63@gmail.com>). The other RFC patch
"rebase: fix advice when a fixup creates an empty commit" [1] could do
with someone commenting on it (I've Cc'd dscho and Elijah). I think the
messages in it could be improved, but if the idea of different messages
for fixups that make a commit empty is not popular then the rest of the
series can be simplified by dropping some earlier patches including
patch 6 which you had some doubts about. (I tired to address those
<141f95b0-cae0-06f6-2c29-618dc22ae000@gmail.com> but I don't know if I
convinced you)
Best Wishes
Phillip
[1]
https://lore.kernel.org/git/20191206160614.631724-9-phillip.wood123@gmail.com/
next prev parent reply other threads:[~2020-02-21 16:26 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
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 [this message]
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
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=e9984c53-7266-c438-87f5-7f5474e3adce@gmail.com \
--to=phillip.wood123@gmail.com \
--cc=Johannes.Schindelin@gmx.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=newren@gmail.com \
--cc=phillip.wood@dunelm.org.uk \
/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).