From: Ramsay Jones <ramsay@ramsay1.demon.co.uk>
To: Christopher Li <sparse@chrisli.org>
Cc: Josh Triplett <josh@joshtriplett.org>,
Sparse Mailing-list <linux-sparse@vger.kernel.org>
Subject: Re: [PATCH 3/5] Makefile: suppress error message from shell
Date: Fri, 24 Jul 2009 19:40:22 +0100 [thread overview]
Message-ID: <4A6A0016.5030204@ramsay1.demon.co.uk> (raw)
In-Reply-To: <70318cbf0907211735t6e279f5ag5602abd54f94656f@mail.gmail.com>
Christopher Li wrote:
> On Tue, Jul 21, 2009 at 2:50 PM, Ramsay Jones<ramsay@ramsay1.demon.co.uk> wrote:
>> Hmm, I noticed that you edited the "subject line" when you applied
>> the patch; namely s/shell/pkg-config/.
>>
>> I find this a little puzzling, since the error message *is* issued
>> by the shell and is definitely *not* issued by pkg-config... which
>> is kinda the point... ;-)
>>
> Oh, right. The error is issue from shell when it try to run pkg-config.
> If I just read the title, it is hard for me to predict where the change
> is going to be. I just want to be more specific.
>
> There is a reason I haven't push those to official tree yet. We can
> still change it if we want. Suggestion?
I liked the original myself. :)
The "Makefile:" prefix was intended to indicate where the change was
made and I thought that the one-line summary was compact and accurate.
It's a bit difficult to indicate that "the cause of the error, which
is issued by the shell, is a missing pkg-config command on some
systems" as part of the one-line summary. (So I didn't try ;P )
Having said that, I can't claim to be good at writing commit messages.
So, feel free to re-write it as you wish.
ATB,
Ramsay Jones
prev parent reply other threads:[~2009-07-24 19:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-07-18 20:42 [PATCH 3/5] Makefile: suppress error message from shell Ramsay Jones
2009-07-19 14:03 ` Josh Triplett
2009-07-20 20:21 ` Christopher Li
2009-07-21 21:50 ` Ramsay Jones
2009-07-22 0:35 ` Christopher Li
2009-07-24 18:40 ` Ramsay Jones [this message]
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=4A6A0016.5030204@ramsay1.demon.co.uk \
--to=ramsay@ramsay1.demon.co.uk \
--cc=josh@joshtriplett.org \
--cc=linux-sparse@vger.kernel.org \
--cc=sparse@chrisli.org \
/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