From: Junio C Hamano <junkio@cox.net>
To: David Greaves <david@dgreaves.com>
Cc: Petr Baudis <pasky@ucw.cz>, git@vger.kernel.org
Subject: Re: [FILES] core-git documentation update
Date: Sun, 08 May 2005 12:30:20 -0700 [thread overview]
Message-ID: <7vpsw15xdf.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <427E4F6C.6090302@dgreaves.com> (David Greaves's message of "Sun, 08 May 2005 18:42:04 +0100")
>>>>> "DG" == David Greaves <david@dgreaves.com> writes:
DG> it just makes across the board changes easier and at the minute the
DG> stuff I've been doing is systemic.
DG> I have no problems with breaking it up - hence the script...
Monolithic version is easier to work with when there is only one
or very few people working on it but when the document matures
enough to describe the current state of affairs accurately
enough, further changes would come almost solely from changing
the programs the document describes. At that point having
separate files describing each program is easier to work with,
and I think that point is now.
next prev parent reply other threads:[~2005-05-08 19:27 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
2005-05-08 19:30 ` Junio C Hamano [this message]
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=7vpsw15xdf.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=david@dgreaves.com \
--cc=git@vger.kernel.org \
--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 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.