From: Michal Marek <mmarek@suse.cz>
To: Roland Dreier <roland@kernel.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] setlocalversion: Use "grep -q" instead of piping output to "read dummy"
Date: Mon, 26 Mar 2012 22:58:04 +0200 [thread overview]
Message-ID: <20120326205804.GE10259@sepie.suse.cz> (raw)
In-Reply-To: <1332520947-22172-1-git-send-email-roland@kernel.org>
On Fri, Mar 23, 2012 at 09:42:27AM -0700, Roland Dreier wrote:
> From: Roland Dreier <roland@purestorage.com>
>
> In some circumstances (eg when running a build in an emacs shell
> buffer), I get a spew of messages like
>
> grep: writing output: Broken pipe
>
> from setlocalversion, because the "read" subshell apparently exits as
> soon as it reads one line and gives EPIPE to grep. It's not clear to
> me why this way of writing the check was used instead of just using
> grep -q to suppress output, but unless there is some deep reason I
> don't know, this way looks cleaner to me anyway, and gets rid of the
> ugly message spew.
I guess the author was used to write it this way, because ancient grep
versions did not have -q.
> (I double checked at http://pubs.opengroup.org/onlinepubs/009604499/utilities/grep.html
> and "grep -q" is specified in POSIX / SuS, so hopefully even people
> cross-compiling the kernel on some bizarre host OS can't complain
> about this change)
Yeah, I think it's safe. Thanks for double-checking.
Applied to kbuild.git#kbuild now.
Michal
prev parent reply other threads:[~2012-03-26 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-23 16:42 [PATCH] setlocalversion: Use "grep -q" instead of piping output to "read dummy" Roland Dreier
2012-03-26 20:58 ` Michal Marek [this message]
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=20120326205804.GE10259@sepie.suse.cz \
--to=mmarek@suse.cz \
--cc=linux-kernel@vger.kernel.org \
--cc=roland@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