From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 1/4] Add option -r to env import to allow import of text files with CRLF as line endings
Date: Mon, 04 Aug 2014 21:18:49 +0200 [thread overview]
Message-ID: <53DFDC99.2020206@ahsoftware.de> (raw)
In-Reply-To: <yw1x4mxs60co.fsf@unicorn.mansr.com>
Am 04.08.2014 12:00, schrieb M?ns Rullg?rd:
> Alexander Holler <holler@ahsoftware.de> writes:
> Why not just make "env import" treat \r like any other whitespace? It
> would be a slight change from current behaviour, but the chance that
> someone actually relies on a trailing \r being part of the value is
> vanishingly small.
There was an objection about such wheh I've first posted the patch
whichg already has had the same strong check as the current patch. But I
think nobody still has a problem with that, and whatever was said long
time ago was based on some misunderstandings about what the patch is
for, and how it really works and how the new feature is used.
And currently we are only talking if and how enhancing "env export".
At least I've understood it such that nobody still has an objection
against the new feature for "env import -t" (-r).
Regards,
Alexander Holler
next prev parent reply other threads:[~2014-08-04 19:18 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-07-14 15:49 [U-Boot] [PATCH 0/4] Add option -r to env import to allow import of text files with CRLF as line endings Alexander Holler
2014-07-14 15:49 ` [U-Boot] [PATCH 1/4] " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
2014-07-30 22:47 ` [U-Boot] [PATCH " Stephen Warren
2014-07-31 19:51 ` Tom Rini
2014-07-31 19:57 ` Stephen Warren
2014-08-14 8:25 ` Alexander Holler
2014-08-14 15:49 ` Stephen Warren
2014-08-14 18:41 ` Robert Nelson
2014-08-14 19:38 ` Tom Rini
2014-08-14 19:50 ` Stephen Warren
2014-08-14 20:53 ` Tom Rini
2014-08-14 21:05 ` Alexander Holler
2014-08-14 21:35 ` Stephen Warren
2014-08-14 21:44 ` Alexander Holler
2014-08-14 19:38 ` Alexander Holler
2014-08-14 19:51 ` Stephen Warren
2014-08-14 19:59 ` Alexander Holler
2014-08-14 20:08 ` Stephen Warren
2014-08-14 20:39 ` Alexander Holler
2014-08-01 12:08 ` Wolfgang Denk
2014-08-02 21:09 ` Alexander Holler
2014-08-03 16:38 ` Alexander Holler
2014-08-03 17:51 ` Wolfgang Denk
2014-08-04 6:47 ` Alexander Holler
2014-08-04 7:00 ` Alexander Holler
2014-08-04 10:00 ` Måns Rullgård
2014-08-04 19:18 ` Alexander Holler [this message]
2014-08-06 6:43 ` Wolfgang Denk
2014-08-06 10:02 ` Alexander Holler
2014-08-06 10:28 ` Alexander Holler
2014-08-06 10:44 ` Måns Rullgård
2014-08-06 11:18 ` Alexander Holler
2014-08-06 11:48 ` Alexander Holler
2014-08-03 17:47 ` Wolfgang Denk
2014-07-14 15:49 ` [U-Boot] [PATCH 2/4] omap3_beagle: handle import of environments in " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
2014-07-14 15:49 ` [U-Boot] [PATCH 3/4] am335x_evm: " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
2014-07-14 15:49 ` [U-Boot] [PATCH 4/4] rpi_b: " Alexander Holler
2014-07-22 19:23 ` [U-Boot] [U-Boot, " Tom Rini
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=53DFDC99.2020206@ahsoftware.de \
--to=holler@ahsoftware.de \
--cc=u-boot@lists.denx.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