From: "Martin Ågren" <martin.agren@gmail.com>
To: "Jean-Noël Avila" <avila.jn@gmail.com>
Cc: Eric Sunshine <sunshine@sunshineco.com>, Git List <git@vger.kernel.org>
Subject: Re: [PATCH 2/7] git-bugreport.txt: fix reference to strftime(3)
Date: Mon, 18 May 2020 13:15:49 +0200 [thread overview]
Message-ID: <CAN0heSpu7yjB0aJRuRhU+dncDryTRkMq4+B_D4BHBav5YoD1gw@mail.gmail.com> (raw)
In-Reply-To: <96735cc6-35d6-f94d-75d5-d6d4df1aefa0@gmail.com>
On Mon, 18 May 2020 at 12:54, Jean-Noël Avila <avila.jn@gmail.com> wrote:
>
> On Mon, 18 May 2020, Martin Ågren, Eric Sunshine wrote:
> > On Sun, 17 May 2020 at 21:23, Eric Sunshine <sunshine@sunshineco.com> wrote:
> >> On Sun, May 17, 2020 at 2:52 PM Martin Ågren <martin.agren@gmail.com> wrote:
> >>> When we say "link:strftime[3]", it ends up rendered as "3[1]" and we
> >>> produce a footnote referring to the non-existing
> >>> file:///.../git-doc/strftime. Make sure we use gitlink, not link, to get
> >> s/gitlink/linkgit/
> > Oops, thanks! At least the diff is correct.
>
> Not even sure of that: strftime is not an internal manpage, so for html
> target, we will end up with a hyperlink to an non-existing file
> strftime.html. So I would keep it as simple text.
That's a good point. I don't use the HTML versions myself, so I haven't
thought about the *linking* nature much -- I just see the formatting.
But you're right. Grepping around, we only seem to use linkgit to refer
to our own docs. So this should probably just be "strftime(3)" as you
say.
Thanks,
Martin
next prev parent reply other threads:[~2020-05-18 11:15 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-17 18:52 [PATCH 0/7] Documentation fixes for v2.27.0-rc0 Martin Ågren
2020-05-17 18:52 ` [PATCH 1/7] date-formats.txt: fix list continuation Martin Ågren
2020-05-17 18:52 ` [PATCH 2/7] git-bugreport.txt: fix reference to strftime(3) Martin Ågren
2020-05-17 19:23 ` Eric Sunshine
2020-05-17 19:27 ` Martin Ågren
2020-05-18 10:54 ` Jean-Noël Avila
2020-05-18 11:15 ` Martin Ågren [this message]
2020-05-17 18:52 ` [PATCH 3/7] git-commit-graph.txt: fix grammo Martin Ågren
2020-05-18 14:46 ` Derrick Stolee
2020-05-17 18:52 ` [PATCH 4/7] git-commit-graph.txt: fix list rendering Martin Ågren
2020-05-17 18:52 ` [PATCH 5/7] git-credential.txt: use list continuation Martin Ågren
2020-05-18 23:06 ` Carlo Marcelo Arenas Belón
2020-05-17 18:52 ` [PATCH 6/7] git-sparse-checkout.txt: add missing ' Martin Ågren
2020-05-18 14:46 ` Derrick Stolee
2020-05-17 18:52 ` [PATCH 7/7] rev-list-options.txt Martin Ågren
2020-05-18 14:57 ` Derrick Stolee
2020-05-18 18:37 ` Martin Ågren
2020-05-18 20:22 ` Junio C Hamano
2020-05-25 17:06 ` [PATCH v2] rev-list-options.txt: start a list for `show-pulls` Martin Ågren
2020-05-26 12:24 ` Derrick Stolee
2020-05-26 19:18 ` Martin Ågren
2020-05-26 15:16 ` Junio C Hamano
2020-05-26 17:01 ` Derrick Stolee
2020-05-26 19:20 ` Martin Ågren
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=CAN0heSpu7yjB0aJRuRhU+dncDryTRkMq4+B_D4BHBav5YoD1gw@mail.gmail.com \
--to=martin.agren@gmail.com \
--cc=avila.jn@gmail.com \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.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).