From mboxrd@z Thu Jan 1 00:00:00 1970 From: Alexander Holler Date: Mon, 04 Aug 2014 09:00:03 +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: <53DF2C9A.6080805@ahsoftware.de> 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: <53DF2F73.5080002@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 08:47, schrieb Alexander Holler: > But it would not be really symmetric. The -r for "env import" makes "env > import" eat both formats, which means it can be used almost always, but > using -r with "env export" would be a decision which always would be > wrong for many people. > > Of course, adding the possibility to export the environment in a > system-foreign format (Assuming nobody boots windows using u-boot) > doesn't really make a harm, it just adds the danger that people will use > -r for "env export" because it is used for "env import" too, which most > likely would be wrong for most usage scenarios. > > Anyway, I don't have any other objections agains a -r for "env export", > maybe it could be added to the TODO-list which contains documentation > for "env *" too. ;) My slow brain (therefor this second message) now suggests to add e.g. a -w to "env export", where the -w would be mutually exclusive to -t. This would make it clear that it doesn't mean the same as '-t -r' for env import and that using -w means a decision which might be wrong. Regards, Alexander Holler