From: David Woodhouse <dwmw2@infradead.org>
To: Satyam Sharma <satyam@infradead.org>
Cc: Sam Ravnborg <sam@ravnborg.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Make headers_check less chatty for success cases
Date: Tue, 31 Jul 2007 17:30:09 +0100 [thread overview]
Message-ID: <1185899409.3083.122.camel@pmac.infradead.org> (raw)
In-Reply-To: <alpine.LFD.0.999.0707312206140.28746@enigma.security.iitk.ac.in>
On Tue, 2007-07-31 at 22:10 +0530, Satyam Sharma wrote:
> "make headers_check" is too verbose. It likes to chat even if it has
> just _successfully_ checked a header, and not just on seeing errors.
> What is worse, even if you touch just one little header in some corner
> (or possibly none) and type "make" on an "already-made" tree,
> headers_check still feels obliged to check all the headers.
Didn't Sam have a better fix for that?
--
dwmw2
next prev parent reply other threads:[~2007-07-31 16:30 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-31 16:40 [PATCH] Make headers_check less chatty for success cases Satyam Sharma
2007-07-31 16:30 ` David Woodhouse [this message]
2007-07-31 16:54 ` Sam Ravnborg
2007-07-31 17:01 ` Satyam Sharma
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=1185899409.3083.122.camel@pmac.infradead.org \
--to=dwmw2@infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=sam@ravnborg.org \
--cc=satyam@infradead.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