From: Sascha Hauer <s.hauer@pengutronix.de>
To: Gerd Pauli <gp@high-consulting.de>
Cc: barebox@lists.infradead.org
Subject: Re: [PATCH v1] writef: added command to write content of variable to file
Date: Mon, 16 Oct 2017 10:38:34 +0200 [thread overview]
Message-ID: <20171016083834.tayzv4vxenid5pe7@pengutronix.de> (raw)
In-Reply-To: <1507278196-15424-1-git-send-email-gp@high-consulting.de>
On Fri, Oct 06, 2017 at 10:23:16AM +0200, Gerd Pauli wrote:
> writef: added command to write content of variable to file.
> Adds a newline at the emd of the string.
>
> Usage: writef VAR FILE
Do we need this command at all? It could be replaced with
echo -o FILE $foo
no?
Sascha
--
Pengutronix e.K. | |
Industrial Linux Solutions | http://www.pengutronix.de/ |
Peiner Str. 6-8, 31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-5555 |
_______________________________________________
barebox mailing list
barebox@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/barebox
prev parent reply other threads:[~2017-10-16 8:38 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-06 8:23 Gerd Pauli
2017-10-16 8:38 ` Sascha Hauer [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=20171016083834.tayzv4vxenid5pe7@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=gp@high-consulting.de \
/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