From: "Carlo Marcelo Arenas Belón" <carenas@gmail.com>
To: git@vger.kernel.org
Cc: hanwen@google.com
Subject: Re: [PATCH] reftable: technical documentation link fixes
Date: Mon, 25 May 2020 15:00:57 -0700 [thread overview]
Message-ID: <20200525220057.GA69013@Carlos-MBP> (raw)
In-Reply-To: <20200525210232.87550-1-carenas@gmail.com>
Forgot to mention, the third URL wasn't updated since it was somehow not
affected, while the first one wasn't affected when using Asciidoctor 2.0.10.
The middle one always breaks (even with Asciidoctor) because of the "="
character, so the "minimal" change needed will be to URL encode that as %3D
or use "link" as proposed in the patch.
Carlo
next prev parent reply other threads:[~2020-05-25 22:01 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-25 21:02 [PATCH] reftable: technical documentation link fixes Carlo Marcelo Arenas Belón
2020-05-25 22:00 ` Carlo Marcelo Arenas Belón [this message]
2020-05-26 18:53 ` Han-Wen Nienhuys
2020-05-26 23:16 ` Carlo Marcelo Arenas Belón
2020-05-27 2:21 ` Jonathan Nieder
2020-05-27 17:14 ` 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=20200525220057.GA69013@Carlos-MBP \
--to=carenas@gmail.com \
--cc=git@vger.kernel.org \
--cc=hanwen@google.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 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 NNTP newsgroup(s).