All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Julia Evans" <julia@jvns.ca>
To: "Omri Sarig" <omri.sarig13@gmail.com>,
	"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 09:06:35 -0500	[thread overview]
Message-ID: <eaa965fa-05fa-4945-aacb-2fc99b02159d@app.fastmail.com> (raw)
In-Reply-To: <20261101082230.141688-1-omri.sarig13@gmail.com>

> @@ -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.

Elsewhere in the document we're now linking to the section like this,
since 2fc11e33820:

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.

  parent reply	other threads:[~2026-11-10 14:06 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 [this message]
2026-11-10 15:37     ` Omri Sarig
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=eaa965fa-05fa-4945-aacb-2fc99b02159d@app.fastmail.com \
    --to=julia@jvns.ca \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=me@linux.beauty \
    --cc=omri.sarig13@gmail.com \
    --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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.