From: "Štěpán Němec" <stepnem@gmail.com>
To: Jonathan Nieder <jrnieder@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: The linkgit: Asciidoc macro broken (for some backends)?
Date: Thu, 04 Nov 2010 23:49:26 +0100 [thread overview]
Message-ID: <87sjzgg0w9.fsf@gmail.com> (raw)
In-Reply-To: <20101104222159.GB18475@burratino> (Jonathan Nieder's message of "Thu, 4 Nov 2010 17:23:18 -0500")
Jonathan Nieder <jrnieder@gmail.com> writes:
>> I noticed that even though all the links to gitrevisions(7) in the
>> documentation sources point correctly to manual section 7 (where it
>> belongs and is actually installed), the links are rendered in manpages
>> as gitrevisions(1)
>
> Probably your copy of the reference manual precedes v1.7.3.2~12 (Documentation:
> gitrevisions is in section 7, 2010-10-11).
Ah, so it _is_ a PEBKAC after all... I was wondering :-)
Thank you and sorry for the noise.
Štěpán
prev parent reply other threads:[~2010-11-04 22:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-11-04 22:10 The linkgit: Asciidoc macro broken (for some backends)? Štěpán Němec
2010-11-04 22:23 ` Jonathan Nieder
2010-11-04 22:49 ` Štěpán Němec [this message]
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=87sjzgg0w9.fsf@gmail.com \
--to=stepnem@gmail.com \
--cc=git@vger.kernel.org \
--cc=jrnieder@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 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).