From: Bernd Petrovitsch <bernd@firmix.at>
To: Daniel Walker <dwalker@mvista.com>
Cc: Jiri Slaby <jirislaby@gmail.com>,
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 11:11:03 +0100 [thread overview]
Message-ID: <1200046263.10166.9.camel@tara.firmix.at> (raw)
In-Reply-To: <1200044878.29897.78.camel@imap.mvista.com>
On Fre, 2008-01-11 at 01:47 -0800, Daniel Walker wrote:
> On Fri, 2008-01-11 at 10:41 +0100, Jiri Slaby wrote:
> > On 01/11/2008 10:36 AM, Daniel Walker wrote:
> > > On Fri, 2008-01-11 at 10:34 +0100, Jiri Slaby wrote:
> > >> 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 ..
> >
> > OK, maybe we should base it in doc for patch submitting then?
>
> It's in the bash docs I'm sure, it's just a matter of who ends up
Yes, too. And "awk" also supports that.
But "/dev/stdin" is also since ages a symlink to
"/proc/self/fd/0" (which is another equivalent "file").
> reading that part of the docs.. I still think my patch is a good one ,
> we could change the name to "Allow piping with out tricks" I suppose ..
Bernd
--
Firmix Software GmbH http://www.firmix.at/
mobil: +43 664 4416156 fax: +43 1 7890849-55
Embedded Linux Development and Services
next prev parent reply other threads:[~2008-01-11 10:11 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080111041030.043498178@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 [this message]
2008-01-11 11:16 ` Stefan Richter
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=1200046263.10166.9.camel@tara.firmix.at \
--to=bernd@firmix.at \
--cc=apw@shadowen.org \
--cc=dwalker@mvista.com \
--cc=jirislaby@gmail.com \
--cc=jschopp@austin.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=rdunlap@xenotime.net \
/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®