On 2/20/20 5:28 AM, Verma, Vishal L wrote:
> On Wed, 2020-02-19 at 12:09 -0800, Dan Williams wrote:
>>>>
>>>> Let's do a compromise, because users also hate nonsensical legacy that
>>>> they can't avoid. How about an environment variable,
>>>> "NDCTL_LIST_LINT", that users can set to opt into the latest /
>>>> cleanest output format with the understanding that the clean up may
>>>> regress scripts that were dependent on the old bugs.
>>>>
>>> Hm, this sounds good in concept, but how about waiting for this cleanup
>>> to go in after the (yes, long pending) config rework. Then this can just
>>> be a global config setting, and we won't have config things coming from
>>> the environment as well (which this would be a first of).
>>
>> That does make some sense, but I notice that git deals with "cosmetic"
>> environment variables (GIT_EDITOR, GIT_PAGER, etc) in addition to its
>> config file. So if we're borrowing from git, I'd also borrow that
>> config vs environment logic.
>
> True, that's reasonable. I guess I was hoping to avoid, if we can,
> suddenly having a multitude of config sources, but env variables are
> pretty standard and it should be fine to add them.
Hi,
I am sorry for suspending the ndctl global config patch for such a long
time. If it is not urgent, I would like to implement it.
Thank you.
QI fuli
> _______________________________________________
> Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
> To unsubscribe send an email to linux-nvdimm-le...@lists.01.org
>
_______________________________________________
Linux-nvdimm mailing list -- linux-nvdimm@lists.01.org
To unsubscribe send an email to linux-nvdimm-le...@lists.01.org
