LKML Archive on lore.kernel.org
help / color / mirror / Atom feed
From: Daniel Walker <dwalker@mvista.com>
To: Stefan Richter <stefanr@s5r6.in-berlin.de>
Cc: Andy Whitcroft <apw@shadowen.org>,
	Bernd Petrovitsch <bernd@firmix.at>,
	linux-kernel@vger.kernel.org, Randy Dunlap <rdunlap@xenotime.net>,
	Joel Schopp <jschopp@austin.ibm.com>,
	Jiri Slaby <jirislaby@gmail.com>
Subject: Re: [PATCH] checkpatch.pl: show how to read from stdin
Date: Fri, 11 Jan 2008 09:39:51 -0800	[thread overview]
Message-ID: <1200073192.29897.95.camel@imap.mvista.com> (raw)
In-Reply-To: <4787A787.2000503@s5r6.in-berlin.de>


On Fri, 2008-01-11 at 18:29 +0100, Stefan Richter wrote:
> Daniel Walker wrote:
> > On Fri, 2008-01-11 at 18:06 +0100, Stefan Richter wrote:
> >> Signed-off-by: Stefan Richter <stefanr@s5r6.in-berlin.de>
> >> +	print "When patchfile is -, read standard input.\n";
> 
> > Naww .. Why add documentation when you can just make it do the right
> > thing ..
> 
> Why add code for a feature which already exists?

To make it simpler to use .. A good percentage (if not all) command line
unix data processing utils accept piped data directly, without the need
for the "-" .. That's the expect usage .. checkpatch.pl doesn't need to
deviate from the norm, there is no size constraint, there is no line
limit .. So we're not duplicating functionality, we're making the tool
conform ..

Daniel


  reply	other threads:[~2008-01-11 17:41 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 ` [PATCH] checkpatch.pl: allow piping 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
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 [this message]
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=1200073192.29897.95.camel@imap.mvista.com \
    --to=dwalker@mvista.com \
    --cc=apw@shadowen.org \
    --cc=bernd@firmix.at \
    --cc=jirislaby@gmail.com \
    --cc=jschopp@austin.ibm.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=rdunlap@xenotime.net \
    --cc=stefanr@s5r6.in-berlin.de \
    --subject='Re: [PATCH] checkpatch.pl: show how to read from stdin' \
    /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).