From: Omri Sarig <omri.sarig13@gmail.com>
To: git@vger.kernel.org
Cc: Omri Sarig <omri.sarig13@gmail.com>,
Phillip Wood <phillip.wood@dunelm.org.uk>,
Jeff King <peff@peff.net>, Junio C Hamano <gitster@pobox.com>,
Julia Evans <julia@jvns.ca>, Li Chen <me@linux.beauty>
Subject: [PATCH v2] doc: git-rebase: Update incompatible options
Date: Mon, 19 Oct 2026 16:35:45 +0200 [thread overview]
Message-ID: <20261019143546.207295-1-omri.sarig13@gmail.com> (raw)
Several options in the rebase man page link to the "INCOMPATIBLE
OPTIONS" section when the option is no-longer incompatible with any
other option.
- Commit 1a66d8c6f6 (rebase: remove --allow-empty-message from
incompatible opts, 2023-01-25) removed "--allow-empty-message" from
the INCOMPATIBLE OPTIONS section, but did not remove the link to that
section from the option description.
- Commit a74b35081c (rebase: drop support for `--preserve-merges`,
2021-09-07) removed the `--preserve-merges` option from rebase, which
removes all incompatbiilty references to `--ignore-date,
--reset-author-date` and `--signoff`.
Additionally, `--onto` doesn't link to the INCOMPATIBLE OPTIONS section, even
though it is incompatible with `--keep-base`.
Update the description of these option, to have correct references to
the INCOMPATIBLE OPTIONS section.
Signed-off-by: Omri Sarig <omri.sarig13@gmail.com>
---
Changes in V2:
- Update commit message per the review comments from Phillip (Thanks for the
review!).
- Add `--onto` to INCOMPATIEBLE OPTIONS.
I was not sure if both adding INCOMPATIBLE OPTIONS (--onto) and removing them
(the other flags) belong in the same commit, or in 2 separate commits. These
changes felt small enough to me to not require a second commit, but please let
me know if it's preferred. I'll happily send a new patch where these changes
are split across different commits.
Documentation/git-rebase.adoc | 8 ++------
1 file changed, 2 insertions(+), 6 deletions(-)
diff --git a/Documentation/git-rebase.adoc b/Documentation/git-rebase.adoc
index 6536ebdc90..6363b1a096 100644
--- a/Documentation/git-rebase.adoc
+++ b/Documentation/git-rebase.adoc
@@ -218,6 +218,8 @@ OPTIONS
As a special case, you may use "A\...B" as a shortcut for the
merge base of A and B if there is exactly one merge base. You can
leave out at most one of A and B, in which case it defaults to HEAD.
++
+See also <<INCOMPATIBLE_OPTIONS,INCOMPATIBLE OPTIONS>> below.
See <<TRANSPLANTING,TRANSPLANTING A TOPIC BRANCH WITH --ONTO>>
above for examples.
@@ -334,8 +336,6 @@ See also <<INCOMPATIBLE_OPTIONS,INCOMPATIBLE OPTIONS>> below.
and this option would override that behavior, allowing commits
with empty messages to be rebased. Now commits with an empty
message do not cause rebasing to halt.
-+
-See also <<INCOMPATIBLE_OPTIONS,INCOMPATIBLE OPTIONS>> below.
-m::
--merge::
@@ -489,15 +489,11 @@ applying (in terms of the author date).
Instead of using the author date of the original commit, use
the current time as the author date of the rebased commit. This
option implies `--force-rebase`.
-+
-See also <<INCOMPATIBLE_OPTIONS,INCOMPATIBLE OPTIONS>> below.
--signoff::
Add a `Signed-off-by` trailer to all the rebased commits. Note
that if `--interactive` is given then only commits marked to be
picked, edited or reworded will have the trailer added.
-+
-See also <<INCOMPATIBLE_OPTIONS,INCOMPATIBLE OPTIONS>> below.
--trailer=<trailer>::
Append the given trailer to every rebased commit message, processed
Range-diff against v1:
1: 27c94f5ff4 = 1: 27c94f5ff4 doc: git-rebase: Update incompatible options
next reply other threads:[~2026-10-19 14:38 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-19 14:35 Omri Sarig [this message]
2026-10-20 2:29 ` [PATCH v2] doc: git-rebase: Update incompatible options Junio C Hamano
2026-10-20 9:39 ` Phillip Wood
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=20261019143546.207295-1-omri.sarig13@gmail.com \
--to=omri.sarig13@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=julia@jvns.ca \
--cc=me@linux.beauty \
--cc=peff@peff.net \
--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