From: Ingo Molnar <mingo@elte.hu>
To: Andy Whitcroft <andyw@uk.ibm.com>
Cc: Arjan van de Ven <arjan@linux.intel.com>, linux-kernel@vger.kernel.org
Subject: Re: Make checkpatch.pl's quiet option not print the summary on no errors
Date: Tue, 15 Jan 2008 22:58:35 +0100 [thread overview]
Message-ID: <20080115215835.GB2665@elte.hu> (raw)
In-Reply-To: <20080115201054.GC21511@shadowen.org>
* Andy Whitcroft <andyw@uk.ibm.com> wrote:
> On Thu, Jan 03, 2008 at 01:54:42AM +0100, Arjan van de Ven wrote:
> > Subject: Make checkpatch.pl's quiet option not print the summary on no
> > errors
> > From: Arjan van de Ven <arjan@linux.intel.com>
> > CC: apw@uk.ibm.com
> >
> > Right now, in quiet mode, checkpatch.pl still prints a summary line
> > even if the patch is 100% clean. IMO, "quiet mode" should mean "no
> > output if clean", the patch below makes that so. (This also makes
> > the quilt integration on my system work nicer :)
> >
> > Signed-off-by: Arjan van de Ven <arjan@linux.intel.com>
>
> While looking to integrate this I discovered that the current default
> was a desired feature requested by Ingo. So I guess we need to come
> up with a combination of options which give us both.
feel free to drop the summary line on -q, i think i only wanted the
summary to be avilable _somewhere_, so that there's a "quality metric at
glance" line that one can see. To me that still plays OK with quilt
because it's a constant reminder that the patch is clean.
Ingo
next prev parent reply other threads:[~2008-01-15 21:58 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-01-03 0:54 Arjan van de Ven
2008-01-03 13:09 ` Andy Whitcroft
2008-01-15 20:10 ` Andy Whitcroft
2008-01-15 21:58 ` Ingo Molnar [this message]
2008-01-16 11:06 ` Ingo Molnar
2008-01-17 17:05 ` Andy Whitcroft
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=20080115215835.GB2665@elte.hu \
--to=mingo@elte.hu \
--cc=andyw@uk.ibm.com \
--cc=arjan@linux.intel.com \
--cc=linux-kernel@vger.kernel.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
all inboxes | Powered by JetHome®