From: Quint Guvernator <quintus.public@gmail.com>
To: Eric Sunshine <sunshine@sunshineco.com>
Cc: Junio C Hamano <gitster@pobox.com>,
Git Mailing List <git@vger.kernel.org>
Subject: Re: [PATCH 1/1] general style: replaces memcmp() with starts_with()
Date: Mon, 17 Mar 2014 22:33:30 -0400 [thread overview]
Message-ID: <CALs4jVFVO8Jf-nn0PMtOYeMMKsB869KWQv8vV5kAg1itC1isiQ@mail.gmail.com> (raw)
In-Reply-To: <CAPig+cRGwBV5CE3X9yGZGRNtKojCagz_F_f4Kd+S+D_qX+ZwJw@mail.gmail.com>
2014-03-17 21:59 GMT-04:00 Eric Sunshine <sunshine@sunshineco.com>:
> I can't speak for Junio, but the description could be made more
> concise and to-the-point. Aside from using imperative voice, you can
> eliminate redundancy, some of which comes from repeating in prose what
> the patch itself already states more concisely and precisely, and some
> from repeating what is implied by the fact that you're making such a
> change in the first place.
Wow, thanks for the detailed review. This mail will be something to
which I can refer when making future changes.
> In the subject, "general style" is a bit unusual. This isn't just a
> stylistic change; it's intended to improve code clarity.
It felt a little awkward, but I was trying to follow our guide [1] for
commit messages. It is all right to omit the leading identifier?
[1]: https://github.com/git/git/blob/fca26a/Documentation/SubmittingPatches#L87-L116
> A patch of this nature doesn't require much more description than
> stating what it does ("replace memcmp() with starts_with()") and why
> ("improve code clarity"). The following rewrite might be sufficient:
>
> Subject: replace memcmp() with starts_with()
>
> starts_with() indicates the intention of the check more clearly
> than memcmp().
This is more concise; thank you. I will adapt this as the message for
the next version of this patch. Would it be wise to mention magic
numbers, as the discussion surrounding the rationale of this patch,
especially with Junio and Michael, has centered around that?
Thank you for the feedback,
Quint
next prev parent reply other threads:[~2014-03-18 2:33 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-17 21:52 [PATCH v4 0/1] general style: replaces memcmp() with starts_with() Quint Guvernator
2014-03-17 21:52 ` [PATCH 1/1] " Quint Guvernator
2014-03-17 22:52 ` Junio C Hamano
2014-03-17 23:01 ` Jeff King
2014-03-17 23:07 ` Junio C Hamano
2014-03-18 2:41 ` Jeff King
2014-03-17 23:46 ` Quint Guvernator
2014-03-18 1:59 ` Eric Sunshine
2014-03-18 2:33 ` Quint Guvernator [this message]
2014-03-18 4:07 ` Eric Sunshine
2014-03-18 19:23 ` Junio C Hamano
2014-03-17 21:53 ` [PATCH v4 0/1] " Quint Guvernator
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=CALs4jVFVO8Jf-nn0PMtOYeMMKsB869KWQv8vV5kAg1itC1isiQ@mail.gmail.com \
--to=quintus.public@gmail.com \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=sunshine@sunshineco.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).