On Tue, Sep 6, 2016 at 9:02 PM, Erik Mackdanz wrote:
> Kristian Fiskerstrand writes:
>> inherited eclasses. having a whitelist in place and die if eclass is not
>> updated to handle it solves it.
>>
>> Thoughts? comments? cookies? threats?
>
> Wouldn't a
Kristian Fiskerstrand writes:
> inherited eclasses. having a whitelist in place and die if eclass is not
> updated to handle it solves it.
>
> Thoughts? comments? cookies? threats?
Wouldn't a blacklist be more practical than a whitelist?
root# cat
On Tue, 6 Sep 2016 09:19:42 -0400
Rich Freeman wrote:
> On Tue, Sep 6, 2016 at 8:51 AM, Kristian Fiskerstrand wrote:
> >
> > I believe you're overthinking it, if we make it a guideline to include a
> > section of the eclass (as many already have) that does e.g
On 09/06/2016 03:38 PM, M. J. Everitt wrote:
> On 06/09/16 14:35, Kristian Fiskerstrand wrote:
>> On 09/06/2016 03:19 PM, Rich Freeman wrote:
>>> On Tue, Sep 6, 2016 at 8:51 AM, Kristian Fiskerstrand
>>> wrote:
I believe you're overthinking it, if we make it a guideline to
On 09/06/2016 03:19 PM, Rich Freeman wrote:
> On Tue, Sep 6, 2016 at 8:51 AM, Kristian Fiskerstrand wrote:
>>
>> I believe you're overthinking it, if we make it a guideline to include a
>> section of the eclass (as many already have) that does e.g (take this
>> for example
On 09/06/2016 12:44 PM, Kent Fredric wrote:
> On Mon, 5 Sep 2016 15:03:36 +0200
> Michał Górny wrote:
>
>> On Fri, 2 Sep 2016 18:13:20 +0200
>> Kristian Fiskerstrand wrote:
>>
>>> I'm wondering whether it wouldn't make sense to require eclasses (or
>>>
On Mon, 5 Sep 2016 15:03:36 +0200
Michał Górny wrote:
> On Fri, 2 Sep 2016 18:13:20 +0200
> Kristian Fiskerstrand wrote:
>
> > I'm wondering whether it wouldn't make sense to require eclasses (or
> > strongly encourage) to include an explicit list of EAPIs
On Mon, 5 Sep 2016 10:45:30 -0400
Mike Gilbert wrote:
> On Mon, Sep 5, 2016 at 5:20 AM, Alexis Ballier
> wrote:
> > On Fri, 2 Sep 2016 19:19:16 +0200
> > Kristian Fiskerstrand wrote:
> >
> >> On 09/02/2016 07:17 PM, Rich Freeman
On Mon, Sep 5, 2016 at 5:20 AM, Alexis Ballier wrote:
> On Fri, 2 Sep 2016 19:19:16 +0200
> Kristian Fiskerstrand wrote:
>
>> On 09/02/2016 07:17 PM, Rich Freeman wrote:
>> > On Fri, Sep 2, 2016 at 12:53 PM, Alexis Ballier
>> > wrote:
On Mon, 5 Sep 2016 14:58:29 +0200
Michał Górny wrote:
> On Mon, 5 Sep 2016 11:20:29 +0200
> Alexis Ballier wrote:
>
> > On Fri, 2 Sep 2016 19:19:16 +0200
> > Kristian Fiskerstrand wrote:
> >
> > > On 09/02/2016 07:17 PM, Rich Freeman
On Fri, 2 Sep 2016 18:13:20 +0200
Kristian Fiskerstrand wrote:
> I'm wondering whether it wouldn't make sense to require eclasses (or
> strongly encourage) to include an explicit list of EAPIs it has been
> tested for in order to ease testing when introducing new EAPIs.
>
> We
On Mon, 5 Sep 2016 11:20:29 +0200
Alexis Ballier wrote:
> On Fri, 2 Sep 2016 19:19:16 +0200
> Kristian Fiskerstrand wrote:
>
> > On 09/02/2016 07:17 PM, Rich Freeman wrote:
> > > On Fri, Sep 2, 2016 at 12:53 PM, Alexis Ballier
> > >
On Fri, 2 Sep 2016 19:19:16 +0200
Kristian Fiskerstrand wrote:
> On 09/02/2016 07:17 PM, Rich Freeman wrote:
> > On Fri, Sep 2, 2016 at 12:53 PM, Alexis Ballier
> > wrote:
> >> On Fri, 2 Sep 2016 18:13:20 +0200
> >> Kristian Fiskerstrand
On 09/02/2016 07:17 PM, Rich Freeman wrote:
> On Fri, Sep 2, 2016 at 12:53 PM, Alexis Ballier wrote:
>> On Fri, 2 Sep 2016 18:13:20 +0200
>> Kristian Fiskerstrand wrote:
>>
>>> Hi Devs,
>>>
>>> I'm wondering whether it wouldn't make sense to require eclasses
On Fri, 2 Sep 2016 18:13:20 +0200
Kristian Fiskerstrand wrote:
> Hi Devs,
>
> I'm wondering whether it wouldn't make sense to require eclasses (or
> strongly encourage) to include an explicit list of EAPIs it has been
> tested for in order to ease testing when introducing new
15 matches
Mail list logo