From: "Steve Hoelzer" <shoelzer@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] Try to be consistent with capitalization in the documentation
Date: Wed, 1 Aug 2007 12:17:52 -0500 [thread overview]
Message-ID: <588192970708011017q12c7a6d9s532c8aed086d3032@mail.gmail.com> (raw)
In-Reply-To: <7vir7z5gx7.fsf@assigned-by-dhcp.cox.net>
On 8/1/07, Junio C Hamano <gitster@pobox.com> wrote:
> Steve Hoelzer <shoelzer@gmail.com> writes:
>
> > Signed-off-by: Steve Hoelzer <shoelzer@gmail.com>
> > ---
> >
> > Try to be consistent with capitalization in the documentation.
>
> It looks like that all the originals are trying to consistently
> start with lowercase in an explanatory list. Is this really
> needed?
The lists I changed were indeed all lowercase, but other lists in
those files are all uppercase. I was aiming for consistency across all
list items and all lists.
Steve
next prev parent reply other threads:[~2007-08-01 17:18 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-08-01 15:43 [PATCH] Try to be consistent with capitalization in the documentation Steve Hoelzer
2007-08-01 17:00 ` Junio C Hamano
2007-08-01 17:17 ` Steve Hoelzer [this message]
2007-08-02 6:11 ` Junio C Hamano
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=588192970708011017q12c7a6d9s532c8aed086d3032@mail.gmail.com \
--to=shoelzer@gmail.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).