From: Michael J Gruber <git@drmicha.warpmail.net>
To: Jakub Narebski <jnareb@gmail.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: What's cooking in git.git (Feb 2011, #04; Wed, 16)
Date: Thu, 17 Feb 2011 13:20:28 +0100 [thread overview]
Message-ID: <4D5D128C.1080808@drmicha.warpmail.net> (raw)
In-Reply-To: <m3aahu987n.fsf@localhost.localdomain>
Jakub Narebski venit, vidit, dixit 17.02.2011 13:06:
> Junio C Hamano <gitster@pobox.com> writes:
>
>> * mg/placeholders-are-lowercase (2011-02-15) 4 commits
>> - Make <identifier> lowercase as per CodingGuidelines
>> - Make <identifier> lowercase as per CodingGuidelines
>> - Make <identifier> lowercase as per CodingGuidelines
>> - CodingGuidelines: downcase placeholders in usage messages
>>
>> Will merge to 'next'.
>
> Hmmm... three different commits with the _same_ subject?
How would you even know they are different, since you neither read the
commit messages nor looked up the thread? Thomas Rast's work makes the
latter even simpler these days.
Just to save everyone else the pain:
For easier review, the commits are split by the grep expression which
was used to identify candidates for the substitution. They may be
squashed, of course. (Adding "part 1" etc. wouldn't have clarified
anything, and our subjects are length limited.)
Michael
next prev parent reply other threads:[~2011-02-17 12:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-16 23:23 What's cooking in git.git (Feb 2011, #04; Wed, 16) Junio C Hamano
2011-02-17 12:06 ` Jakub Narebski
2011-02-17 12:20 ` Michael J Gruber [this message]
2011-02-20 11:54 ` Sverre Rabbelier
2011-02-21 9:33 ` Michael J Gruber
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=4D5D128C.1080808@drmicha.warpmail.net \
--to=git@drmicha.warpmail.net \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.com \
--cc=jnareb@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.