From: Junio C Hamano <junkio@cox.net>
To: "J. Bruce Fields" <bfields@citi.umich.edu>
Cc: git@vger.kernel.org, Johannes Schindelin <Johannes.Schindelin@gmx.de>
Subject: Re: [PATCH 02/10] user-manual: revise birdseye-view chapter
Date: Mon, 14 May 2007 17:07:04 -0700 [thread overview]
Message-ID: <7v4pmflzkn.fsf@assigned-by-dhcp.cox.net> (raw)
In-Reply-To: <30964.7168651738$1179156134@news.gmane.org> (J. Bruce Fields's message of "Mon, 14 May 2007 11:21:21 -0400")
"J. Bruce Fields" <bfields@citi.umich.edu> writes:
> From: J. Bruce Fields <bfields@citi.umich.edu>
>
> Some revisions suggested by Junio along with some minor style fixes and
> one compile fix (asterisks need escaping).
>
> Cc: Johannes Schindelin <Johannes.Schindelin@gmx.de>
> Signed-off-by: "J. Bruce Fields" <bfields@citi.umich.edu>
> ---
> Documentation/user-manual.txt | 43 +++++++++++++++++++---------------------
> 1 files changed, 20 insertions(+), 23 deletions(-)
>
> diff --git a/Documentation/user-manual.txt b/Documentation/user-manual.txt
> index bac9660..7abdc3e 100644
> --- a/Documentation/user-manual.txt
> +++ b/Documentation/user-manual.txt
> @@ -3161,8 +3161,12 @@ contrast, running "git prune" while somebody is actively changing the
> repository is a *BAD* idea).
>
> [[birdview-on-the-source-code]]
> -A birdview on Git's source code
> ------------------------------
> +A birds-eye view of Git's source code
> +-------------------------------------
> +
> +It is not always easy for new developers to find their way through Git's
> +source code. This section gives you a gentle guidance to show where to
> +start.
>
> While Git's source code is quite elegant, it is not always easy for
> new developers to find their way through it. A good idea is to look
Perhaps you meant to drop this first sentence "While ... through
it." from the original?
next prev parent reply other threads:[~2007-05-15 0:07 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <11791560893572-git-send-email->
2007-05-14 15:21 ` [PATCH 02/10] user-manual: revise birdseye-view chapter J. Bruce Fields
2007-05-15 0:07 ` Junio C Hamano [this message]
2007-05-15 2:58 ` J. Bruce Fields
[not found] ` <1179156089759-git-send-email->
2007-05-14 15:21 ` [PATCH 03/10] glossary: expand and clarify some definitions, prune cross-references J. Bruce Fields
2007-05-14 17:00 ` Jakub Narebski
2007-05-17 4:30 ` J. Bruce Fields
[not found] ` <11791560893022-git-send-email->
2007-05-14 15:21 ` [PATCH 04/10] user-manual: move quick-start to an appendix J. Bruce Fields
[not found] ` <11791560891179-git-send-email->
2007-05-14 15:21 ` [PATCH 05/10] Documentation: remove howto's now incorporated into manual J. Bruce Fields
[not found] ` <1179156089470-git-send-email->
2007-05-14 15:21 ` [PATCH 06/10] user-manual: move howto/make-dist.txt into user manual J. Bruce Fields
[not found] ` <11791560892667-git-send-email->
2007-05-14 15:21 ` [PATCH 07/10] user-manual: move howto/using-topic-branches into manual J. Bruce Fields
[not found] ` <11791560901-git-send-email->
2007-05-14 15:21 ` [PATCH 08/10] user-manual: add a "counting commits" example J. Bruce Fields
[not found] ` <11791560901645-git-send-email->
2007-05-14 15:21 ` [PATCH 09/10] user-manual: introduce git J. Bruce Fields
[not found] ` <1179156090113-git-send-email->
2007-05-14 15:21 ` [PATCH 10/10] user-manual: listing commits reachable from some refs not others J. Bruce Fields
2007-05-14 16:30 ` [PATCH 07/10] user-manual: move howto/using-topic-branches into manual Luck, Tony
2007-05-14 17:11 ` [PATCH] user-manual: fix origin/linus confusion in topic-branches example J. Bruce Fields
2007-05-14 17:44 ` [PATCH 06/10] user-manual: move howto/make-dist.txt into user manual Linus Torvalds
2007-05-14 21:39 ` 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=7v4pmflzkn.fsf@assigned-by-dhcp.cox.net \
--to=junkio@cox.net \
--cc=Johannes.Schindelin@gmx.de \
--cc=bfields@citi.umich.edu \
--cc=git@vger.kernel.org \
/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).