Greetings, Serge E. Hallyn!
>> Add something like "lxc.hooks.legacy" key in some future 2.x version, default
>> to enabled, and recommend people turning it off and see if their hooks needs
>> correction.
>> In some version prior to 3.0, change the default value of the key to
>> disabled.
>> In 3.
Quoting Andrey Repin (anrdae...@yandex.ru):
> Greetings, Christian Brauner!
>
> >> Maybe a configuration key 'lxc.hooks.version=2' ?
>
> > I'm fine with simply keeping the arguments until 3.0 and then removing
> > them. I
> > really don't want to add configuration keys that conceptually are inte
Greetings, Christian Brauner!
>> Maybe a configuration key 'lxc.hooks.version=2' ?
> I'm fine with simply keeping the arguments until 3.0 and then removing them. I
> really don't want to add configuration keys that conceptually are internal
> keys
> but are nonetheless exposed to users. Fwiw, th
On do, 2017-10-05 at 10:27 +0200, Christian Brauner wrote:
> On Wed, Oct 04, 2017 at 09:35:25AM -0500, Serge Hallyn wrote:
> >
> > Quoting Kees Bos (cornelis@gmail.com):
> > >
> > > I'm not using it, but do expect the extra args:
> > >
> > > while [ {{ '${#@}' }} -gt 3 ] ; do
> > > ...
>
On Wed, Oct 04, 2017 at 09:35:25AM -0500, Serge Hallyn wrote:
> Quoting Kees Bos (cornelis@gmail.com):
> > I'm not using it, but do expect the extra args:
> >
> > while [ {{ '${#@}' }} -gt 3 ] ; do
> > ...
> > shift
> > done
> >
> > It might be that some users will need the last extra a
