Git development
 help / color / mirror / Atom feed
From: Phillip Wood <phillip.wood123@gmail.com>
To: Omri Sarig <omri.sarig13@gmail.com>, git@vger.kernel.org
Cc: Jeff King <peff@peff.net>, Julia Evans <julia@jvns.ca>,
	Li Chen <me@linux.beauty>,
	Phillip Wood <phillip.wood@dunelm.org.uk>,
	Junio C Hamano <gitster@pobox.com>
Subject: Re: [PATCH] doc: git-rebase: Update incompatible options
Date: Mon, 19 Oct 2026 14:15:39 +0100	[thread overview]
Message-ID: <921b3a6e-5d3f-4c75-97c6-35da57c6d76f@gmail.com> (raw)
In-Reply-To: <20261018132541.131506-1-omri.sarig13@gmail.com>

Hi Omri

On 18/10/2026 14:25, Omri Sarig wrote:
> Several options in the rebase man page were described as incompatible,
> where this is no longer the case:

Our convention is to use the present tense when describing the current 
situation so we'd say

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 1a66d8c6f658051a02b6d8f024e80e06fccdcd11 removed
>    `--allow-empty-message` for the incompatible option list, but did not
>    update the the documentation of the option itself.

It is very helpful to link to the commit that introduced the change like 
this, but we format commit references in commit messages with "git log 
--format=reference" so this would be

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 a74b35081c51adbde3ef01870ba03e859db33be6 removed the
>    `--preserve-merges` option from rebase, which removes all
>    incompatbiilty references to `--ignore-date, --reset-author-date` and
>    `--signoff`.

The same applies here

> Update the description of these option, to no longer reference the
> INCOMPATIBLE OPTIONS section.

Excellent
> Signed-off-by: Omri Sarig <omri.sarig13@gmail.com>
> ---
> 
> I've also found out that the option `--onto` is now mentioned in the
> INCOMPATIBLE OPTIONS section, but is not referencing it from its own
> documentation. If this is not intentional, I'll happily send another patch/V2
> to address this issue as well.

"--onto" is incompatible with "--keep-base" and "--keep-base" links to 
INCOMPATIBLE OPTIONS so "--onto" should probably do so too.

The changes below all look correct, thanks for improving the documentation.

Phillip

>   Documentation/git-rebase.adoc | 6 ------
>   1 file changed, 6 deletions(-)
> 
> diff --git a/Documentation/git-rebase.adoc b/Documentation/git-rebase.adoc
> index 6536ebdc90..9fd3cf8ce2 100644
> --- a/Documentation/git-rebase.adoc
> +++ b/Documentation/git-rebase.adoc
> @@ -334,8 +334,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 +487,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


      reply	other threads:[~2026-10-19 13:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-18 13:25 [PATCH] doc: git-rebase: Update incompatible options Omri Sarig
2026-10-19 13:15 ` Phillip Wood [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=921b3a6e-5d3f-4c75-97c6-35da57c6d76f@gmail.com \
    --to=phillip.wood123@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=julia@jvns.ca \
    --cc=me@linux.beauty \
    --cc=omri.sarig13@gmail.com \
    --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