From: Junio C Hamano <gitster@pobox.com>
To: "Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com>
Cc: git@vger.kernel.org, Phillip Wood <phillip.wood@dunelm.org.uk>
Subject: Re: [PATCH v2] rebase -i: reword empty commit after fast-forward
Date: Tue, 11 Feb 2025 09:51:55 -0800 [thread overview]
Message-ID: <xmqq8qqcz7wk.fsf@gitster.g> (raw)
In-Reply-To: <pull.1860.v2.git.1739289549299.gitgitgadget@gmail.com> (Phillip Wood via GitGitGadget's message of "Tue, 11 Feb 2025 15:59:08 +0000")
"Phillip Wood via GitGitGadget" <gitgitgadget@gmail.com> writes:
> As "git commit" will happily create empty merge commits without
> "--allow-empty" we do not need to pass that flag when rewording merge
> commits.
Thanks, will queue. Let's mark it for 'next'.
prev parent reply other threads:[~2025-02-11 17:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-02-05 10:37 [PATCH] rebase -i: reword empty commit after fast-forward Phillip Wood via GitGitGadget
2025-02-05 18:26 ` Junio C Hamano
2025-02-11 15:59 ` [PATCH v2] " Phillip Wood via GitGitGadget
2025-02-11 17:51 ` Junio C Hamano [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=xmqq8qqcz7wk.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitgitgadget@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.
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).