From: Junio C Hamano <gitster@pobox.com>
To: "D. Ben Knoble" <ben.knoble+github@gmail.com>
Cc: git@vger.kernel.org, Christian Couder <chriscool@tuxfamily.org>,
Kristoffer Haugsbakk <code@khaugsbakk.name>,
Elijah Newren <newren@gmail.com>,
"brian m. carlson" <sandals@crustytoothpaste.net>,
Sergey Organov <sorganov@gmail.com>
Subject: Re: [PATCH] replay: drop rev-list formatting options from manual
Date: Tue, 20 Jan 2026 13:49:21 -0800 [thread overview]
Message-ID: <xmqq3440x8da.fsf@gitster.g> (raw)
In-Reply-To: <xmqq5x8w2t3o.fsf@gitster.g> (Junio C. Hamano's message of "Tue, 20 Jan 2026 07:37:15 -0800")
Junio C Hamano <gitster@pobox.com> writes:
> "D. Ben Knoble" <ben.knoble+github@gmail.com> writes:
>
>> If I've understood all that correctly, then I have the Python version
>> installed for building Git and it understood the syntax. Given that
>> the Ruby version is newer, I think it should also work against the
>> spec.
>
> We have CI jobs to catch the differences so hopefully we know soon
> enough if one is so badly broken ;-)
>
> Thanks.
We didn't have to wait for CI jobs. You can try
make -C Documentation lint-docs
which reveals that somebody is not expecting these multiple things
there. I think Documentation/lint-gitlink.perl needs updating.
next prev parent reply other threads:[~2026-01-20 21:49 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-01-20 1:47 [PATCH] replay: drop rev-list formatting options from manual D. Ben Knoble
2026-01-20 2:19 ` Junio C Hamano
2026-01-20 14:04 ` D. Ben Knoble
2026-01-20 15:37 ` Junio C Hamano
2026-01-20 21:49 ` Junio C Hamano [this message]
2026-01-20 23:11 ` Junio C Hamano
2026-01-21 13:27 ` Jean-Noël Avila
2026-01-21 16:26 ` Junio C Hamano
2026-01-21 20:03 ` D. Ben Knoble
2026-01-27 18:48 ` D. Ben Knoble
2026-01-20 14:05 ` [PATCH v2] " D. Ben Knoble
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=xmqq3440x8da.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=ben.knoble+github@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=code@khaugsbakk.name \
--cc=git@vger.kernel.org \
--cc=newren@gmail.com \
--cc=sandals@crustytoothpaste.net \
--cc=sorganov@gmail.com \
/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.