From: Alexander Holler <holler@ahsoftware.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 2/2] beagle: handle import of environments in files with CRLF as line endings
Date: Sun, 13 May 2012 20:58:44 +0200 [thread overview]
Message-ID: <4FB00464.7030907@ahsoftware.de> (raw)
In-Reply-To: <201205132052.49764.marex@denx.de>
On 13.05.2012 20:52, Marek Vasut wrote:
> Dear Alexander Holler,
>
>> On 13.05.2012 19:09, Marek Vasut wrote:
>>> Dear Alexander Holler,
>>>
>>>> Use the new option -r for env import.
>>>>
>>>> Signed-off-by: Alexander Holler<holler@ahsoftware.de>
>>>> ---
>>>>
>>>> include/configs/omap3_beagle.h | 2 +-
>>>> 1 files changed, 1 insertions(+), 1 deletions(-)
>>>>
>>>> diff --git a/include/configs/omap3_beagle.h
>>>> b/include/configs/omap3_beagle.h index ddeb414..d8b10c2 100644
>>>> --- a/include/configs/omap3_beagle.h
>>>> +++ b/include/configs/omap3_beagle.h
>>>> @@ -258,7 +258,7 @@
>>>>
>>>> "bootenv=uEnv.txt\0" \
>>>> "loadbootenv=fatload mmc ${mmcdev} ${loadaddr} ${bootenv}\0" \
>>>> "importbootenv=echo Importing environment from mmc ...; " \
>>>>
>>>> - "env import -t $loadaddr $filesize\0" \
>>>> + "env import -t -r $loadaddr $filesize\0" \
>>>
>>> Not everyone importing env on beagle use broken tools ;-)
>>
>> Who said that?
>
> You impose your -r option on all beagle users. That means everyone (even those
> with not-broken) tools will now use it (unless they replaced their env).
Yes, and now they all will get doomed by ignored CRs before LFs.
Anyway, just ignore those patches, it was lost time from the beginning
and I should have known it better.
Alexander
next prev parent reply other threads:[~2012-05-13 18:58 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-13 12:50 [U-Boot] [PATCH 1/2] Add option -r to env import to allow import of text files with CRLF as line endings Alexander Holler
2012-05-13 12:50 ` [U-Boot] [PATCH 2/2] beagle: handle import of environments in " Alexander Holler
2012-05-13 17:09 ` Marek Vasut
2012-05-13 17:56 ` Alexander Holler
2012-05-13 18:52 ` Marek Vasut
2012-05-13 18:58 ` Alexander Holler [this message]
2012-05-13 18:49 ` Wolfgang Denk
2012-05-13 18:57 ` Marek Vasut
2012-05-13 19:26 ` Wolfgang Denk
2012-05-13 19:45 ` Marek Vasut
2012-05-13 19:53 ` Wolfgang Denk
2012-05-13 20:18 ` Alexander Holler
2012-05-13 21:38 ` Wolfgang Denk
2012-05-14 8:29 ` Alexander Holler
2012-05-14 9:07 ` Alexander Holler
2012-05-14 9:21 ` Alexander Holler
2012-05-13 21:47 ` Måns Rullgård
2012-05-14 16:02 ` Tom Rini
2012-05-14 17:04 ` Alexander Holler
2012-05-14 18:45 ` Marek Vasut
2012-05-14 22:23 ` Alexander Holler
2012-05-13 12:58 ` [U-Boot] [PATCH 1/2 v2] Add option -r to env import to allow import of text " Alexander Holler
2012-05-13 18:45 ` [U-Boot] [PATCH 1/2] " Wolfgang Denk
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=4FB00464.7030907@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