From: Junio C Hamano <gitster@pobox.com>
To: Tuomas Ahola <taahol@utu.fi>
Cc: git@vger.kernel.org, "Jean-Noël Avila" <jn.avila@free.fr>,
"Jeff King" <peff@peff.net>
Subject: Re: [PATCH (RESEND)] ci: use system asciidoctor
Date: Fri, 11 Sep 2026 14:50:47 -0700 [thread overview]
Message-ID: <xmqqy0d78nk8.fsf@gitster.g> (raw)
In-Reply-To: <20260911213338.kLh69%taahol@utu.fi> (Tuomas Ahola's message of "Sat, 12 Sep 2026 00:33:38 +0300")
Tuomas Ahola <taahol@utu.fi> writes:
> These two were indeed merged:
>
> * 4340a709bf (ci: fix missing Ruby dependency in "documentation" job, 2026-09-01)
> * 1c1eed13bd (ci: drop ALREADY_HAVE_ASCIIDOCTOR variable, 2026-09-02)
>
> But this is a third one (ci: use system asciidoctor)---it seems it was never
> picked up.
Ahh, that was originally 3 patch series. I see where it went wrong.
Let's queue it on top.
Thanks.
next prev parent reply other threads:[~2026-09-11 21:50 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-01 8:16 [PATCH] ci: fix missing Ruby dependency in "documentation" job Patrick Steinhardt
2026-09-01 8:24 ` Toon Claes
2026-09-01 8:36 ` Patrick Steinhardt
2026-09-01 8:47 ` Jeff King
2026-09-01 8:51 ` Jeff King
2026-09-01 10:41 ` Patrick Steinhardt
2026-09-02 7:11 ` [PATCH 0/2] bump ci asciidoctor version Jeff King
2026-09-02 7:14 ` [PATCH 1/2] ci: drop ALREADY_HAVE_ASCIIDOCTOR variable Jeff King
2026-09-02 7:16 ` [PATCH 2/2] ci: use system asciidoctor Jeff King
2026-09-02 7:55 ` Patrick Steinhardt
2026-09-02 9:01 ` Jeff King
2026-09-02 9:59 ` Patrick Steinhardt
2026-09-05 14:02 ` Jeff King
2026-09-05 15:23 ` Todd Zullinger
2026-09-11 20:42 ` Jeff King
2026-09-11 19:52 ` [PATCH (RESEND)] " Tuomas Ahola
2026-09-11 20:38 ` Jeff King
2026-09-11 20:58 ` Junio C Hamano
2026-09-11 21:33 ` Tuomas Ahola
2026-09-11 21:50 ` Junio C Hamano [this message]
2026-09-01 17:58 ` [PATCH] ci: fix missing Ruby dependency in "documentation" job 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=xmqqy0d78nk8.fsf@gitster.g \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=jn.avila@free.fr \
--cc=peff@peff.net \
--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.