[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <1200043827.29897.70.camel@imap.mvista.com>
Date: Fri, 11 Jan 2008 01:30:27 -0800
From: Daniel Walker <dwalker@...sta.com>
To: Bernd Petrovitsch <bernd@...mix.at>
Cc: Jiri Slaby <jirislaby@...il.com>, apw@...dowen.org,
linux-kernel@...r.kernel.org, rdunlap@...otime.net,
jschopp@...tin.ibm.com
Subject: Re: [PATCH] checkpatch.pl: allow piping
On Fri, 2008-01-11 at 10:23 +0100, Bernd Petrovitsch wrote:
> On Fre, 2008-01-11 at 10:21 +0100, Jiri Slaby wrote:
> > On 01/11/2008 10:17 AM, Daniel Walker wrote:
> > > On Fri, 2008-01-11 at 09:52 +0100, Jiri Slaby wrote:
> > >> On 01/11/2008 05:10 AM, Daniel Walker wrote:
> > >>> A little feature addition to allow checkpatch.pl to check
> patches piped
> > >>> into it, in addition to specific file arguments.
> > >> You can still add - as an argument to check stdin. In which way
> is this better?
> > >
> > > There's was no reason to limit the arguments ..
> > >
> > > I was using it to do something like the following ,
> > >
> > > git show 9914cad54c79d0b89b1f066c0894f00e1344131c
> | ./scripts/checkpatch.pl
> >
> > Ok, and if you add a - there, it should have the same effect, but
> for free,
> > doesn't it:
> > git show 9914cad54c79d0b89b1f066c0894f00e1344131c
> | ./scripts/checkpatch.pl -
>
> JftSoC:
> git show 9914cad54c79d0b89b1f066c0894f00e1344131c
> | ./scripts/checkpatch.pl /dev/stdin
> (and there a a few others) should also do the trick.
Not a particularly attractive command line .. Might still be a good idea
to add this since these two forms alluded me, and are likely to allude
people new to unix all together (who is more likely to be using this
particular tool)..
Daniel
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists