From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Mon, 04 Aug 2014 21:18:49 +0200 Subject: [U-Boot] [PATCH 1/4] Add option -r to env import to allow import of text files with CRLF as line endings In-Reply-To: References: <1405352998-7707-1-git-send-email-holler@ahsoftware.de> <1405352998-7707-2-git-send-email-holler@ahsoftware.de> <20140801120800.9BDE438336B@gemini.denx.de> <53DD53A5.3010502@ahsoftware.de> <53DE658F.5010703@ahsoftware.de> <20140803175114.BDAF33812FC@gemini.denx.de> <53DF2C9A.6080805@ahsoftware.de> Message-ID: <53DFDC99.2020206@ahsoftware.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Am 04.08.2014 12:00, schrieb M?ns Rullg?rd: > Alexander Holler 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