All of lore.kernel.org
 help / color / mirror / Atom feed
From: Simon Glass <sjg@chromium.org>
To: Wolfgang Denk <wd@denx.de>
Cc: Tom Rini <trini@konsulko.com>,
	U-Boot Mailing List <u-boot@lists.denx.de>,
	 Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Joe Hershberger <joe.hershberger@ni.com>
Subject: Re: [PATCH v6 4/7] env: Allow U-Boot scripts to be placed in a .env file
Date: Mon, 18 Oct 2021 12:12:16 -0600	[thread overview]
Message-ID: <CAPnjgZ2FGUCFDbSU8TvsV5p-5p3aqnwf7ju28xMKB__w2-ATGw@mail.gmail.com> (raw)
In-Reply-To: <3502270.1634566234@gemini.denx.de>

Hi Wolfgang,

On Mon, 18 Oct 2021 at 08:10, Wolfgang Denk <wd@denx.de> wrote:
>
> Dear Tom,
>
> In message <20211018133728.GQ7964@bill-the-cat> you wrote:
> >
> > > And please see also my comments about changing the autostart
> > > functionality for the user.
> >
> > Perhaps we should just make "+" an illegal character in the variable
> > name, for consistency?
>
> And break backward compatibility?  I'd rather see a better
> definition of the syntax of the environment files, plus maybe a more
> powerful parser.
>
> I mean, there is no technical reason to forbid the '+' character -
> and then it's only at the end of the variable name.
>
> Hm... I can't find it right now but did I not also read about other
> restrictions to variable names, like they must noch begin with '_'
> when using this new tool?

Yes but I took that out (I think in v6). I'll update the commit message.

>
>
> I feel it is wrong to place new restrictions on something that was
> constant for 21 years, just because our parser cannot parse it...

We need the + thing and perhaps we should ask people to avoid
punctuation, etc? But for now I'm not requiring it in this series,
apart from +

Regards,
Simon

  parent reply	other threads:[~2021-10-18 18:13 UTC|newest]

Thread overview: 24+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-10-14 18:22 [PATCH v6 0/7] env: Allow environment in text files Simon Glass
2021-10-14 18:22 ` [PATCH v6 1/7] binman: Allow timeout to occur in the image or its section Simon Glass
2021-10-14 18:22 ` [PATCH v6 2/7] sandbox: Drop distro_boot Simon Glass
2021-10-14 18:22 ` [PATCH v6 3/7] doc: Move environment documentation to rST Simon Glass
2021-10-14 18:22 ` [PATCH v6 4/7] env: Allow U-Boot scripts to be placed in a .env file Simon Glass
2021-10-15 14:32   ` Wolfgang Denk
2021-10-15 15:15     ` Simon Glass
2021-10-18 11:58       ` Wolfgang Denk
2021-10-18 13:37         ` Tom Rini
2021-10-18 14:10           ` Wolfgang Denk
2021-10-18 14:24             ` Tom Rini
2021-10-19 10:33               ` Wolfgang Denk
2021-10-18 18:12             ` Simon Glass [this message]
2021-10-19 10:38               ` Wolfgang Denk
2021-10-18 18:12         ` Simon Glass
2021-10-19 10:46           ` Wolfgang Denk
2021-10-19 14:11             ` Simon Glass
2021-10-19 16:09               ` Wolfgang Denk
2021-10-19 16:14                 ` Simon Glass
2021-10-14 18:22 ` [PATCH v6 5/7] sandbox: Use a text-based environment Simon Glass
2021-10-14 18:22 ` [PATCH v6 6/7] doc: Improve environment documentation Simon Glass
2021-10-14 18:22 ` [PATCH v6 7/7] bootm: Tidy up use of autostart env var Simon Glass
2021-10-15 14:45   ` Wolfgang Denk
2021-10-24 19:53     ` Simon Glass

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=CAPnjgZ2FGUCFDbSU8TvsV5p-5p3aqnwf7ju28xMKB__w2-ATGw@mail.gmail.com \
    --to=sjg@chromium.org \
    --cc=joe.hershberger@ni.com \
    --cc=trini@konsulko.com \
    --cc=u-boot@lists.denx.de \
    --cc=wd@denx.de \
    --cc=xypron.glpk@gmx.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.