git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jeremy White <jwhite@codeweavers.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line'.
Date: Thu, 13 Sep 2012 15:57:39 -0500	[thread overview]
Message-ID: <505248C3.7000803@codeweavers.com> (raw)
In-Reply-To: <7vehm593v8.fsf@alter.siamese.dyndns.org>

Thanks for the feedback; new patch inbound.  Minor nits:

>> diff --git a/Documentation/gitcore-tutorial.txt b/Documentation/gitcore-tutorial.txt
>> index f7815e9..92f97e6 100644
>> --- a/Documentation/gitcore-tutorial.txt
>> +++ b/Documentation/gitcore-tutorial.txt
>> @@ -956,7 +956,7 @@ $ git show-branch --topo-order --more=1 master mybranch
>>  ------------------------------------------------
>>  
>>  The first two lines indicate that it is showing the two branches
>> -and the first line of the commit log message from their
>> +and the first paragraph of the commit log message from their
>>  top-of-the-tree commits, you are currently on `master` branch
>>  (notice the asterisk `\*` character), and the first column for
>>  the later output lines is used to show commits contained in the
> 
> Ditto.

I did not substantially alter this. The emphasis of this section
is on the broader show-branch output, and belaboring the subject would
be distracting and unnecessary imho.

Cheers,

Jeremy

  reply	other threads:[~2012-09-13 20:57 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 12:42 [PATCH] Documentation: Use 'First Paragraph' instead of 'First Line' Jeremy White
2012-09-13 18:25 ` Junio C Hamano
2012-09-13 20:57   ` Jeremy White [this message]
2012-09-13 21:15     ` Junio C Hamano
2012-09-13 21:20       ` Jeremy White
2012-09-13 21:30         ` Junio C Hamano
2012-09-13 22:25           ` Jeremy White
2012-09-13 18:45 ` Philip Oakley

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=505248C3.7000803@codeweavers.com \
    --to=jwhite@codeweavers.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    /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).