From: Jakub Narebski <jnareb@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>
Cc: Junio Hamano <junkio@cox.net>, Pieter de Bie <pdebie@ai.rug.nl>,
Manoj Srivastava <srivasta@ieee.org>,
"Thomas Adam" <thomas.adam22@gmail.com>,
Jeff King <peff@peff.net>,
"J. Bruce Fields" <bfields@fieldses.org>,
git@vger.kernel.org
Subject: Re: [PATCH] Documentation: convert "glossary" and "core-tutorial" to man pages
Date: Sun, 4 May 2008 13:13:01 +0200 [thread overview]
Message-ID: <200805041313.03499.jnareb@gmail.com> (raw)
In-Reply-To: <20080504122157.ca98c75d.chriscool@tuxfamily.org>
On Sun, 4. May 2008, Christian Couder wrote:
> This patch renames the following documents and at the same time converts
> them to the man format:
>
> core-tutorial.txt -> gitcore-tutorial.txt
> glossary.txt -> gitglossary.txt
I like this, although I think that perhaps git-core-tutorial.txt would
be a better filename.
> But as the glossary is included in the user manual and as the new
> gitglossary man page cannot be included as a whole in the user manual,
> the actual glossary content is now in its own "glossary-content.txt"
> new file. And this file is included by both the user manual and the
> gitglossary man page.
Another solution would be to use conditionals. I'm not sure which
one is better; I guess the include one...
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2008-05-04 11:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-04 10:21 [PATCH] Documentation: convert "glossary" and "core-tutorial" to man pages Christian Couder
2008-05-04 11:13 ` Jakub Narebski [this message]
2008-05-04 11:16 ` Pieter de Bie
2008-05-04 12:13 ` Jakub Narebski
2008-05-05 1:50 ` Ping Yin
-- strict thread matches above, loose matches on Subject: below --
2008-05-29 17:21 Christian Couder
2008-05-29 18:39 ` 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=200805041313.03499.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=bfields@fieldses.org \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pdebie@ai.rug.nl \
--cc=peff@peff.net \
--cc=srivasta@ieee.org \
--cc=thomas.adam22@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).