From: Johannes Schindelin <Johannes.Schindelin@gmx.de>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: Junio C Hamano <junkio@cox.net>, git@vger.kernel.org
Subject: Re: [PATCH 6/6] user-manual: stop deprecating the manual
Date: Mon, 7 May 2007 12:57:28 +0200 (CEST) [thread overview]
Message-ID: <Pine.LNX.4.64.0705071256030.4167@racer.site> (raw)
In-Reply-To: <11785148472393-git-send-email->
Hi,
On Mon, 7 May 2007, J. Bruce Fields wrote:
> It's just as much a work-in-progress, but at least now it's gotten
> enough technical review to shake out most of the really bad lies, so
> hopefully it doesn't do any actual damage. And if we encourage people
> to read it, they'll be more likely to whine about it, which will help
> get it fixed faster.
FWIW I am a fan of the user manual. It is much, much better than the
tutorial/manpage combo, when you want to learn how to use Git.
Ciao,
Dscho
next prev parent reply other threads:[~2007-05-07 10:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11785148422793-git-send-email->
2007-05-07 5:13 ` [PATCH 1/6] user-manual: more discussion of detached heads, fix typos J. Bruce Fields
[not found] ` <11785148433801-git-send-email->
2007-05-07 5:13 ` [PATCH 2/6] user-manual: add section ID's J. Bruce Fields
[not found] ` <11785148442263-git-send-email->
2007-05-07 5:13 ` [PATCH 3/6] user-manual: clean up fast-forward and dangling-objects sections J. Bruce Fields
[not found] ` <1178514845119-git-send-email->
2007-05-07 5:14 ` [PATCH 4/6] user-manual: fix .gitconfig editing examples J. Bruce Fields
[not found] ` <11785148452962-git-send-email->
2007-05-07 5:14 ` [PATCH 5/6] user-manual: miscellaneous editing J. Bruce Fields
[not found] ` <11785148461307-git-send-email->
2007-05-07 5:14 ` [PATCH 6/6] user-manual: stop deprecating the manual J. Bruce Fields
[not found] ` <11785148472393-git-send-email->
2007-05-07 10:57 ` Johannes Schindelin [this message]
2007-05-07 19:19 ` Junio C Hamano
2007-05-08 2:49 ` 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=Pine.LNX.4.64.0705071256030.4167@racer.site \
--to=johannes.schindelin@gmx.de \
--cc=bfields@citi.umich.edu \
--cc=git@vger.kernel.org \
--cc=junkio@cox.net \
/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