From: David Greaves <david@dgreaves.com>
To: Petr Baudis <pasky@ucw.cz>
Cc: git@vger.kernel.org, Junio C Hamano <junkio@cox.net>
Subject: Re: [FILES] core-git documentation update
Date: Sun, 08 May 2005 18:42:04 +0100 [thread overview]
Message-ID: <427E4F6C.6090302@dgreaves.com> (raw)
In-Reply-To: <20050508173109.GZ9495@pasky.ji.cz>
Petr Baudis wrote:
>Dear diary, on Sun, May 08, 2005 at 07:22:53PM CEST, I got a letter
>where David Greaves <david@dgreaves.com> told me that...
>
>
>>I've converted the core-git.txt to asciidoc format and created a trivial
>>splitter to create individual txt, html and man pages.
>>
>>
>
>Is there any reason to keep the source in a single huge monolithic file?
>
>
it just makes across the board changes easier and at the minute the
stuff I've been doing is systemic.
I have no problems with breaking it up - hence the script...
David
--
next prev parent reply other threads:[~2005-05-08 17:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-08 17:22 [FILES] core-git documentation update David Greaves
2005-05-08 17:31 ` Petr Baudis
2005-05-08 17:42 ` David Greaves [this message]
2005-05-08 19:30 ` Junio C Hamano
2005-05-08 21:25 ` [BUG] in asciidoc was " David Greaves
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=427E4F6C.6090302@dgreaves.com \
--to=david@dgreaves.com \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@ucw.cz \
/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).