From: Jakub Narebski <jnareb@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: fix git-clone manpage not to refer to itself
Date: Mon, 19 Nov 2007 15:03:00 +0100 [thread overview]
Message-ID: <fhs52j$npp$1@ger.gmane.org> (raw)
In-Reply-To: Pine.LNX.4.64.0711191430460.16728@wbgn129.biozentrum.uni-wuerzburg.de
Johannes Schindelin wrote:
> On Fri, 16 Nov 2007, Sergei Organov wrote:
>
>> +ifndef::git-clone[]
>
> It is laudable that you want to fix the _generated_ documentation, but
> there are two things to keep in mind:
>
> - it does _nothing_ to help readers of the sources, and asciidoc was
> chosen purposely because the source is human-readable, and
IMHO it doesn't make source of documentation less readable.
It has the advantage of not duplicating contents, and being a bit mre
readable than writing "for <cmd>" in documentation contents.
--
Jakub Narebski
Warsaw, Poland
ShadeHawk on #git
next prev parent reply other threads:[~2007-11-19 14:03 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-16 18:43 [PATCH] Documentation: fix git-clone manpage not to refer to itself Sergei Organov
2007-11-19 13:35 ` Johannes Schindelin
2007-11-19 14:03 ` Jakub Narebski [this message]
2007-11-19 19:18 ` Sergei Organov
2007-11-20 9:41 ` Wincent Colaiuta
2007-11-20 11:28 ` Johannes Schindelin
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='fhs52j$npp$1@ger.gmane.org' \
--to=jnareb@gmail.com \
--cc=git@vger.kernel.org \
/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.