From: Eric Sunshine <sunshine@sunshineco.com>
To: Julian Gindi <juliangindi@gmail.com>
Cc: Git List <git@vger.kernel.org>
Subject: Re: [PATCH v2] CodingGuidelines: updating 'rough' rule count
Date: Mon, 13 Apr 2015 01:04:36 -0400 [thread overview]
Message-ID: <CAPig+cQ3z_UuUMZE_jUGbv1_3Fu_32GSw2ysSixw4VE0opz27w@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cTgNzO5NGabOsaSZOq7Y47OBXJz9mnS-MfpoQ2MANzrng@mail.gmail.com>
On Mon, Apr 13, 2015 at 1:00 AM, Eric Sunshine <sunshine@sunshineco.com> wrote:
> On Mon, Apr 13, 2015 at 12:26 AM, Julian Gindi <juliangindi@gmail.com> wrote:
>> Changed inaccurate count of "rough rules" from three to the more
>> generic 'a few'.
>
> Imperative: s/Changed/Change/
I forgot to mention the unusual 2-space indentation of the log
message. It should be left-justified.
next prev parent reply other threads:[~2015-04-13 5:04 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-12 23:47 [PATCH] CodingGuidelines: updating 'rough' rule count Julian Gindi
2015-04-13 0:04 ` Eric Sunshine
2015-04-13 4:26 ` [PATCH v2] " Julian Gindi
2015-04-13 5:00 ` Eric Sunshine
2015-04-13 5:04 ` Eric Sunshine [this message]
2015-04-13 12:54 ` [PATCH v3] CodingGuidelines: update " Julian Gindi
2015-04-13 17:30 ` Jonathan Nieder
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=CAPig+cQ3z_UuUMZE_jUGbv1_3Fu_32GSw2ysSixw4VE0opz27w@mail.gmail.com \
--to=sunshine@sunshineco.com \
--cc=git@vger.kernel.org \
--cc=juliangindi@gmail.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).