Re: [PATCH v2] rebase -i: reword empty commit after fast-forward

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Subject: Re: [PATCH v2] rebase -i: reword empty commit after fast-forward
From: Junio C Hamano <gitster@xxxxxxxxx>
Date: Tue, 11 Feb 2025 09:51:55 -0800
Cc: git@xxxxxxxxxxxxxxx, Phillip Wood <phillip.wood@xxxxxxxxxxxxx>
Feedback-id: if26b431b:Fastmail
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")
References: <pull.1860.git.1738751840816.gitgitgadget@gmail.com> <pull.1860.v2.git.1739289549299.gitgitgadget@gmail.com>
User-agent: Gnus/5.13 (Gnus v5.13)

"Phillip Wood via GitGitGadget" <gitgitgadget@xxxxxxxxx> 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'.

References:
- [PATCH] rebase -i: reword empty commit after fast-forward
  - From: Phillip Wood via GitGitGadget
- [PATCH v2] rebase -i: reword empty commit after fast-forward
  - From: Phillip Wood via GitGitGadget

Prev by Date: Re: [PATCH v2] builtin/refs: add '--skip-reflog' flag to bypass reflog migration
Next by Date: Re: [PATCH v4 0/10] Long names for `git log -S` and `git log -G`
Previous by thread: [PATCH v2] rebase -i: reword empty commit after fast-forward
Next by thread: [PATCH] doc: documentation for http.uploadarchive config option
Index(es):
- Date
- Thread

[Index of Archives] [Linux Kernel Development] [Gcc Help] [IETF Annouce] [DCCP] [Netdev] [Networking] [Security] [V4L] [Bugtraq] [Yosemite] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Linux SCSI] [Fedora Users]

Powered by Linux