Re: [PATCH] env: introduce CONFIG_ENV_DOTVARS_TEMPORARY

2020-01-21 Thread Wolfgang Denk
Dear Rasmus, In message <2676be2b-2e4f-7aba-14e6-5659174ad...@prevas.dk> you wrote: > > > This is not a good idea. The decision whether a variable shall be > > stored permanently or not, or wheter it is readonly or writable, and > > other such properties should never based on their name. > >

Re: [PATCH] env: introduce CONFIG_ENV_DOTVARS_TEMPORARY

2020-01-20 Thread Rasmus Villemoes
On 20/01/2020 17.44, Wolfgang Denk wrote: > Dear Rasmus Villemoes, > > In message <20200108134247.31443-1-rasmus.villem...@prevas.dk> you wrote: >> The printenv command already by default hides variables beginning with >> a dot. It can be useful to take that convention even further, and >>

Re: [PATCH] env: introduce CONFIG_ENV_DOTVARS_TEMPORARY

2020-01-20 Thread Wolfgang Denk
Dear Rasmus Villemoes, In message <20200108134247.31443-1-rasmus.villem...@prevas.dk> you wrote: > The printenv command already by default hides variables beginning with > a dot. It can be useful to take that convention even further, and > prevent such variables from ever being stored

[PATCH] env: introduce CONFIG_ENV_DOTVARS_TEMPORARY

2020-01-08 Thread Rasmus Villemoes
The printenv command already by default hides variables beginning with a dot. It can be useful to take that convention even further, and prevent such variables from ever being stored persistently (and ignored if they happen to exist in stable storage). This way, one can freely use such variable