From: Todd Zullinger <tmz@pobox.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org, "SZEDER Gábor" <szeder.dev@gmail.com>,
"Martin Ågren" <martin.agren@gmail.com>
Subject: Re: What's cooking in git.git (Apr 2019, #01; Thu, 4)
Date: Thu, 4 Apr 2019 21:05:56 -0400 [thread overview]
Message-ID: <20190405010556.GN4047@pobox.com> (raw)
In-Reply-To: <xmqqr2aidpxw.fsf@gitster-ct.c.googlers.com>
Hi Junio,
Junio C Hamano wrote:
> * sg/asciidoctor-in-ci (2019-04-01) 6 commits
> - ci: fix AsciiDoc/Asciidoctor stderr check in the documentation build job
> - ci: stick with Asciidoctor v1.5.8 for now
> - ci: install Asciidoctor in 'ci/install-dependencies.sh'
> - Documentation/technical/protocol-v2.txt: fix formatting
> - Documentation/technical/api-config.txt: fix formatting
> - Documentation/git-diff-tree.txt: fix formatting
>
> Update our support to format documentation in the CI environment,
> either with AsciiDoc ro Asciidoctor.
>
> Will merge to 'next'.
Martin mentioned this in reply to the patch thread¹ but it
looks like it slipped by unnoticed. There's some extraneous
comments in 28216d13f4 ("ci: stick with Asciidoctor v1.5.8
for now", 2019-03-29) which would be good to trim before
this hits next.
commit 28216d13f43b07e41bdd83b786ae31c00c657e06
Author: SZEDER Gábor <szeder.dev@gmail.com>
Date: Fri Mar 29 20:52:46 2019 +0100
ci: stick with Asciidoctor v1.5.8 for now
On Fri, Mar 29, 2019 at 01:35:19PM +0100, SZEDER Gábor wrote:
> The release of Asciidoctor v2.0.0 two days ago broke our documentation
Well, what happened "two days ago" when I sent v2 is now seven days
ago... Let's just say "recent" instead.
--- >8 ---
Subject: ci: stick with Asciidoctor v1.5.8 for now
The recent release of Asciidoctor v2.0.0 broke our documentation
...
¹ <CAN0heSrQrVQ+t3ZH1igU8zZLjjyhzZshFgarLcZOumWMBRN2Tg@mail.gmail.com>
Thanks,
--
Todd
next prev parent reply other threads:[~2019-04-05 1:11 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-04 10:28 What's cooking in git.git (Apr 2019, #01; Thu, 4) Junio C Hamano
2019-04-04 11:08 ` Duy Nguyen
2019-04-04 21:29 ` Junio C Hamano
2019-04-06 20:28 ` Ævar Arnfjörð Bjarmason
2019-04-08 4:14 ` Junio C Hamano
2019-04-09 10:26 ` [PATCH] Introduce "precious" file concept Nguyễn Thái Ngọc Duy
2019-04-09 11:31 ` Junio C Hamano
2019-04-10 9:36 ` Duy Nguyen
2019-04-12 1:28 ` Junio C Hamano
2019-04-09 17:44 ` Eric Sunshine
2019-04-12 21:54 ` Ævar Arnfjörð Bjarmason
2019-04-13 10:19 ` Duy Nguyen
2019-04-05 1:05 ` Todd Zullinger [this message]
2019-04-05 5:41 ` What's cooking in git.git (Apr 2019, #01; Thu, 4) Junio C Hamano
2019-04-06 19:28 ` Ævar Arnfjörð Bjarmason
2019-04-08 4:18 ` Junio C Hamano
2019-04-06 19:57 ` Ævar Arnfjörð Bjarmason
2019-04-08 4:28 ` Junio C Hamano
2019-04-08 21:18 ` Josh Steadmon
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=20190405010556.GN4047@pobox.com \
--to=tmz@pobox.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=martin.agren@gmail.com \
--cc=szeder.dev@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.