From: Philipp-Joachim Ost <pj@smo.de>
To: "Alejandro Colomar" <alx.manpages@gmail.com>,
"Bernhard Voelker" <mail@bernhard-voelker.de>,
"Alex Henrie" <alexhenrie24@gmail.com>,
"Christian Groessler" <chris@groessler.org>,
"Pádraig Brady" <P@draigbrady.com>, Coreutils <coreutils@gnu.org>,
"William Ahern" <william@25thandclement.com>,
"Erik Auerswald" <auerswal@unix-ag.uni-kl.de>,
"Eric Pruitt" <eric.pruitt@gmail.com>,
"Jeffrey Walton" <noloader@gmail.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
Fabrice BAUZAC <noon@mykolab.com>,
tech@openbsd.org, freebsd-hackers@freebsd.org,
linux-api@vger.kernel.org, juli@clockworksquid.com, ed@nuxi.nl,
oshogbo@freebsd.org
Subject: Re: [PATCH v3 (resend)] tee: Add -q, --quiet, --silent option to not write to stdout
Date: Mon, 25 Jan 2021 17:06:24 +0100 [thread overview]
Message-ID: <aa519ecf-b062-3100-f76f-c51c4ca8f497@smo.de> (raw)
In-Reply-To: <20210124121845.38293-1-alx.manpages@gmail.com>
Am 24.01.2021 um 13:18 schrieb Alejandro Colomar:
> This is useful for using tee to just write to a file,
> at the end of a pipeline,
> without having to redirect to /dev/null
>
> Example:
>
> echo 'foo' | sudo tee -q /etc/foo;
>
> is equivalent to the old (and ugly)
>
> echo 'foo' | sudo tee /etc/foo >/dev/null;
Why don't you just do
echo foo > /etc/foo
or
sudo sh -c 'echo foo > /etc/foo' ?
I don't normally use sudo, so there might be some better way of using it.
Kind regards,
Philipp
prev parent reply other threads:[~2021-01-25 16:17 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20210121131735.317701-1-alx.manpages@gmail.com>
[not found] ` <8aa1d0b4-d2ec-7d18-120b-cae59708767c@draigBrady.com>
[not found] ` <424b9fb9-c740-1a2f-bd79-0b4035104698@gmail.com>
[not found] ` <e1a3b389-b808-92db-258d-85b60748b4dc@bernhard-voelker.de>
[not found] ` <06fb3df3-a956-3ec1-eadb-82fd89ec62d5@gmail.com>
[not found] ` <af2fb24a-a03a-35ef-c86e-545844b61a8d@groessler.org>
[not found] ` <CAMMLpeRSh5HKi=sJV7y=pav26EzzP-yEe0+Dgp_=mtBUhtFvaQ@mail.gmail.com>
[not found] ` <3bb6a134-c477-116c-182d-d6e24dc342e0@bernhard-voelker.de>
[not found] ` <f78ec1a9-f07f-de20-26cc-4be254e3e921@gmail.com>
2021-01-21 22:49 ` [PATCH] tee: Add -q, --quiet option to not write to stdout Alejandro Colomar (man-pages)
2021-01-21 23:12 ` [PATCH v2] tee: Add -q, --quiet, --silent " Alejandro Colomar
2021-01-22 18:25 ` Alejandro Colomar (man-pages)
2021-01-23 14:53 ` [PATCH] " Alejandro Colomar
2021-01-24 12:18 ` [PATCH v3 (resend)] " Alejandro Colomar
2021-01-24 16:11 ` Teran McKinney
2021-01-24 16:22 ` Alejandro Colomar (man-pages)
2021-01-24 17:51 ` Otto Moerbeek
2021-01-24 17:58 ` Theo de Raadt
2021-01-24 20:01 ` Alex Henrie
2021-01-24 20:22 ` Otto Moerbeek
2021-01-25 4:03 ` Bernhard Voelker
2021-01-25 11:33 ` Alejandro Colomar (man-pages)
2021-01-26 9:08 ` Alejandro Colomar (man-pages)
2021-01-27 1:40 ` Alex Henrie
2021-03-14 9:44 ` Alejandro Colomar (man-pages)
2021-03-15 17:42 ` Alex Henrie
2021-03-15 20:20 ` Alex Henrie
2021-01-25 16:06 ` Philipp-Joachim Ost [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=aa519ecf-b062-3100-f76f-c51c4ca8f497@smo.de \
--to=pj@smo.de \
--cc=P@draigbrady.com \
--cc=alexhenrie24@gmail.com \
--cc=alx.manpages@gmail.com \
--cc=auerswal@unix-ag.uni-kl.de \
--cc=chris@groessler.org \
--cc=coreutils@gnu.org \
--cc=ed@nuxi.nl \
--cc=eric.pruitt@gmail.com \
--cc=freebsd-hackers@freebsd.org \
--cc=juli@clockworksquid.com \
--cc=linux-api@vger.kernel.org \
--cc=mail@bernhard-voelker.de \
--cc=mtk.manpages@gmail.com \
--cc=noloader@gmail.com \
--cc=noon@mykolab.com \
--cc=oshogbo@freebsd.org \
--cc=tech@openbsd.org \
--cc=william@25thandclement.com \
/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;
as well as URLs for NNTP newsgroup(s).