From: Akira Yokosawa <akiyks@gmail.com>
To: "Paul E. McKenney" <paulmck@kernel.org>
Cc: perfbook@vger.kernel.org, Zhouyi Zhou <zhouzhouyi@gmail.com>,
Akira Yokosawa <akiyks@gmail.com>
Subject: Re: [PATCH -perfbook] bib/perfmeas: Fix doi of McKenney99b
Date: Mon, 24 Jan 2022 08:44:17 +0900 [thread overview]
Message-ID: <bbb86a86-1656-95c6-36a3-e7dbfa030d22@gmail.com> (raw)
In-Reply-To: <9d07bd21-9988-9b1f-d7f1-c7dae07d7a51@gmail.com>
On Fri, 21 Jan 2022 22:32:13 +0900, Akira Yokosawa wrote:
> Escape sequences of "%3C" and "%3E" in doi cause a build error when
> "inlinelinks" option in alphapf.bst is set #0 (URLs explicit).
>
> Fix the error by using non-escaped symbols of "<" and ">" instead.
>
> Fixes: 62c6a33781d9 ("bib: url/doi updates")
> Signed-off-by: Akira Yokosawa <akiyks@gmail.com>
Paul,
You might be confused but I expected you would apply this fix as
well.
Thanks, Akira
> ---
> Hi Zhouyi,
>
> Prompted by your patch "RFC: make some bibliography items better",
> I tested an option in alphapf.bst (bibliography style file of
> perfbook), namely "inlinelinks".
> By setting "#0" to inlinelink (URLs explicit), URL and DOI info
> in .bib files should be printed in Bibliography.
>
> However, the build failed with McKenney99b.
>
> This patch should fix the build error.
>
> You still need to manually edit alphapf.bst, but please try
> setting "#0" to inlinelink.
>
> As you will see, if a bibliography has DOI info, URL info in
> the note field is redundant when the URL is the one reachable
> via the DOI.
>
> Thanks, Akira
> --
> bib/perfmeas.bib | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/bib/perfmeas.bib b/bib/perfmeas.bib
> index 9ba80cfc..51f63bb7 100644
> --- a/bib/perfmeas.bib
> +++ b/bib/perfmeas.bib
> @@ -83,7 +83,7 @@ Machine Language Rewriting",
> year = {1999},
> pages = {219-234},
> bibsource = {DBLP, http://dblp.uni-trier.de},
> - doi = {10.1002/(SICI)1097-024X(199903)29:3%3C219::AID-SPE230%3E3.0.CO;2-0}
> + doi = {10.1002/(SICI)1097-024X(199903)29:3<219::AID-SPE230>3.0.CO;2-0}
> }
>
> @Book{Menasce94,
>
> base-commit: cd891db680ae978f5efa362cbdc074483f07042a
next prev parent reply other threads:[~2022-01-23 23:44 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-21 13:32 [PATCH -perfbook] bib/perfmeas: Fix doi of McKenney99b Akira Yokosawa
2022-01-21 14:16 ` Zhouyi Zhou
2022-01-23 23:44 ` Akira Yokosawa [this message]
2022-01-24 0:18 ` Paul E. McKenney
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=bbb86a86-1656-95c6-36a3-e7dbfa030d22@gmail.com \
--to=akiyks@gmail.com \
--cc=paulmck@kernel.org \
--cc=perfbook@vger.kernel.org \
--cc=zhouzhouyi@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.