From: "J. Bruce Fields" <bfields@fieldses.org>
To: Petr Baudis <pasky@suse.cz>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: Documentation (mainly user-manual) patches
Date: Fri, 18 May 2007 09:43:16 -0400 [thread overview]
Message-ID: <20070518134316.GA21925@fieldses.org> (raw)
In-Reply-To: <20070518045634.GU4489@pasky.or.cz>
On Fri, May 18, 2007 at 06:56:35AM +0200, Petr Baudis wrote:
> BTW, there is this nice git-request-pull tool which will prepare this
> mail for you and additionally include the list of commits included in
> that repository, which is somewhat more friendly to the readers (I
> myself wondered). ;-)
OK! I'll start including the shortlog. Appended, if anyone's still
curious about this one.--b.
J. Bruce Fields (10):
user-manual: revise birdseye-view chapter
glossary: expand and clarify some definitions, prune cross-references
user-manual: move quick-start to an appendix
Documentation: remove howto's now incorporated into manual
user-manual: move howto/make-dist.txt into user manual
user-manual: move howto/using-topic-branches into manual
user-manual: add a "counting commits" example
user-manual: introduce git
user-manual: listing commits reachable from some refs not others
user-manual: reorganize public git repo discussion
Johannes Schindelin (1):
Add a birdview-on-the-source-code section to the user manual
next prev parent reply other threads:[~2007-05-18 13:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-18 3:37 Documentation (mainly user-manual) patches J. Bruce Fields
2007-05-18 3:39 ` [PATCH] user-manual: reorganize public git repo discussion J. Bruce Fields
2007-05-18 4:56 ` Documentation (mainly user-manual) patches Petr Baudis
2007-05-18 13:43 ` J. Bruce Fields [this message]
2007-05-19 4:02 ` Shawn O. Pearce
2007-05-19 4:13 ` J. Bruce Fields
2007-05-19 4:32 ` Shawn O. Pearce
2007-05-19 5:19 ` J. Bruce Fields
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=20070518134316.GA21925@fieldses.org \
--to=bfields@fieldses.org \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
--cc=pasky@suse.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).