LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Stefan Richter <stefanr@s5r6.in-berlin.de>
To: Daniel Walker <dwalker@mvista.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
	Bernd Petrovitsch <bernd@firmix.at>,
	apw@shadowen.org, linux-kernel@vger.kernel.org,
	rdunlap@xenotime.net, jschopp@austin.ibm.com
Subject: Re: [PATCH] checkpatch.pl: allow piping
Date: Fri, 11 Jan 2008 12:16:59 +0100	[thread overview]
Message-ID: <4787502B.2020606@s5r6.in-berlin.de> (raw)
In-Reply-To: <1200044206.29897.73.camel@imap.mvista.com>

Daniel Walker wrote:
> On Fri, 2008-01-11 at 10:34 +0100, Jiri Slaby wrote:
>> >> On Fre, 2008-01-11 at 10:21 +0100, Jiri Slaby wrote:
>> >>> git show 9914cad54c79d0b89b1f066c0894f00e1344131c
>> >> | ./scripts/checkpatch.pl -

>> If somebody is hacking kernel, I think he should know the - trick used in many 
>> programs, but do not consider this as a nack.
> 
> I'm hacking the kernel, and I didn't know the - trick .. So you have
> your testing case all in one with the patch submitter ..

How about

 if ($#ARGV < 0) {
 	print "usage: $P [options] patchfile\n";
 	print "version: $V\n";
 	print "options: -q           => quiet\n";
 	print "         --no-tree    => run without a kernel tree\n";
 	print "         --terse      => one line per report\n";
 	print "         --emacs      => emacs compile window format\n";
 	print "         --file       => check a source file\n";
 	print "         --strict     => enable more subjective tests\n";
 	print "         --root       => path to the kernel tree root\n";
+	print "When patchfile is -, read standard input.\n";
 	exit(1);
 }

-- 
Stefan Richter
-=====-==--- ---= -=-==
http://arcgraph.de/sr/

  parent reply	other threads:[~2008-01-11 11:18 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20080111041120.085610726@mvista.com>
2008-01-11  4:11 ` Daniel Walker
2008-01-11  8:52 ` Jiri Slaby
2008-01-11  9:17   ` Daniel Walker
2008-01-11  9:21     ` Jiri Slaby
2008-01-11  9:23       ` Bernd Petrovitsch
2008-01-11  9:30         ` Daniel Walker
2008-01-11  9:34           ` Jiri Slaby
2008-01-11  9:36             ` Daniel Walker
2008-01-11  9:41               ` Jiri Slaby
2008-01-11  9:47                 ` Daniel Walker
2008-01-11 10:11                   ` Bernd Petrovitsch
2008-01-11 11:16               ` Stefan Richter [this message]
2008-01-11 11:50                 ` Jiri Slaby
2008-01-11 17:06                   ` [PATCH] checkpatch.pl: show how to read from stdin Stefan Richter
2008-01-11 17:09                     ` Daniel Walker
2008-01-11 17:29                       ` Stefan Richter
2008-01-11 17:39                         ` Daniel Walker
2008-01-14 17:17                     ` Andy Whitcroft
2008-01-14 17:35                       ` Daniel Walker
2008-01-14 19:12                         ` Andy Whitcroft
2008-01-14 19:17                           ` Daniel Walker
2008-01-14 19:31                             ` Stefan Richter
2008-01-14 19:44                               ` Jiri Slaby
2008-01-14 19:51                               ` Daniel Walker
2008-01-11 10:08           ` [PATCH] checkpatch.pl: allow piping Bernd Petrovitsch

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=4787502B.2020606@s5r6.in-berlin.de \
    --to=stefanr@s5r6.in-berlin.de \
    --cc=apw@shadowen.org \
    --cc=bernd@firmix.at \
    --cc=dwalker@mvista.com \
    --cc=jirislaby@gmail.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --subject='Re: [PATCH] checkpatch.pl: allow piping' \
    /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

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).