From: Omri Sarig <omri.sarig13@gmail.com>
To: Julia Evans <julia@jvns.ca>, Junio C Hamano <gitster@pobox.com>,
Tuomas Ahola <taahol@utu.fi>
Cc: git@vger.kernel.org, me@linux.beauty, phillip.wood@dunelm.org.uk
Subject: Re: [PATCH v6] doc: git-rebase: update incompatible options
Date: Tue, 10 Nov 2026 16:37:57 +0100 [thread overview]
Message-ID: <b77fcd1c-21aa-4029-91d2-38c89a53f788@gmail.com> (raw)
In-Reply-To: <eaa965fa-05fa-4945-aacb-2fc99b02159d@app.fastmail.com>
On 10/11/2026 15.06, Julia Evans wrote:
>> @@ -217,6 +217,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 below.
Thank you for looking at it!
> Elsewhere in the document we're now linking to the section like this,
> since 2fc11e33820:
As per Junio's request
(https://lore.kernel.org/git/xmqqjyncxrur.fsf@gitster.g/), the current
version is built over the 'maint' branch, and therefore does not have
2fc11e33820 available yet.
I've discussed whether this update should include the links, or not
include them, and understood from Tuomas that the right way to do it
here, is to keep the file consistent with itself in the maintenance
branch version of it, and update the links everywhere in a future patch
(discussed here:
https://lore.kernel.org/git/20261029080317.wWchf%25taahol@utu.fi/).
Additionally, the INCOMPATIBLE OPTIONS section cannot be a target to a
link yet, so this won't apply cleanly to the 'maint' branch with these
links.
Please let me know if I should update these links, or keep them
consistent with the rest of the file in the 'maint' branch.
>
> See also <<INCOMPATIBLE_OPTIONS,INCOMPATIBLE OPTIONS>> below.
>
> I think it would be good to keep things consistent.
>
> Also it would be good to try to convert up all remaining internal links that
> aren't using the << >>, I may try to do that at some point.
As far as I can see, the only place that does not have a link to the
INCOMPATIBLE OPTIONS section in the master branch is the --trailer option.
If you want me to, I'll happily update the added section, together with
the trailer options, once both are merge.
Thanks,
Omri
next prev parent reply other threads:[~2026-11-10 15:38 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-25 11:07 [PATCH v4] doc: git-rebase: update incompatible options Omri Sarig
2026-10-29 8:03 ` Tuomas Ahola
2026-10-30 16:38 ` [PATCH v5] " Omri Sarig
2026-10-30 19:27 ` Tuomas Ahola
2026-10-30 19:31 ` Junio C Hamano
2026-10-30 19:57 ` Tuomas Ahola
2026-11-01 8:22 ` [PATCH v6] " Omri Sarig
2026-11-09 17:23 ` Omri Sarig
2026-11-10 14:06 ` Julia Evans
2026-11-10 15:37 ` Omri Sarig [this message]
2026-11-10 17:59 ` Julia Evans
2026-11-10 18:10 ` Junio C Hamano
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=b77fcd1c-21aa-4029-91d2-38c89a53f788@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=phillip.wood@dunelm.org.uk \
--cc=taahol@utu.fi \
/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