git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: "Martin Ågren" <martin.agren@gmail.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: What's cooking in git.git (Sep 2019, #01; Sat, 7)
Date: Tue, 10 Sep 2019 07:04:24 +0200	[thread overview]
Message-ID: <CAN0heSq9B8NSr7-Bcqpiags6wyMm_3KUGeo+7GZA85nd7GnG=w@mail.gmail.com> (raw)
In-Reply-To: <xmqqd0gcm2zm.fsf@gitster-ct.c.googlers.com>

Hi Junio,

On Sun, 8 Sep 2019 at 14:51, Junio C Hamano <gitster@pobox.com> wrote:
>
> * ma/asciidoctor-refmiscinfo (2019-09-03) 2 commits
>  - doc-diff: replace --cut-header-footer with --cut-footer
>  - asciidoctor-extensions: provide `<refmiscinfo/>`
>
>  Update support for Asciidoctor documentation toolchain.
>
>  Will merge to 'next'.

Please hold off on this. Asciidoctor changed the way they handle these
attributes in version 1.5.7 and my patches are incomplete at best. I
developed these with 1.5.5 and now I am also able to test with 1.5.7.
I should be able to come up with a series that works with both of those
versions.

Martin

  parent reply	other threads:[~2019-09-10  5:04 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-07 17:26 What's cooking in git.git (Sep 2019, #01; Sat, 7) Junio C Hamano
2019-09-09 18:58 ` Denton Liu
2019-09-09 19:57   ` Junio C Hamano
2019-09-10  0:18     ` Denton Liu
2019-09-09 23:47 ` brian m. carlson
2019-09-10  0:19   ` Junio C Hamano
2019-09-28 23:31   ` Junio C Hamano
2019-09-28 23:35     ` brian m. carlson
2019-09-10  5:04 ` Martin Ågren [this message]
2019-09-10 18:23 ` Josh Steadmon
2019-09-11  1:03 ` Matheus Tavares Bernardino
2019-09-11 12:01 ` pd/fetch-jobs, was " Johannes Schindelin
2019-09-12 18:02   ` Junio C Hamano
2019-09-14 13:58     ` Palmer Dabbelt
2019-09-16 17:43       ` Junio C Hamano
2019-09-16 20:40         ` Palmer Dabbelt

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CAN0heSq9B8NSr7-Bcqpiags6wyMm_3KUGeo+7GZA85nd7GnG=w@mail.gmail.com' \
    --to=martin.agren@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).