On 9 July 2016 at 16:32, Pekka Paalanen wrote:
> On Thu, 7 Jul 2016 20:08:40 +0200
> Quentin Glidic wrote:
>
>> On 07/07/2016 18:11, Emil Velikov wrote:
>> > On 7 July 2016 at 10:05, Pekka Paalanen wrote:
>> >>
>> >> [snip]
>> >>
>> >> Now that you mentioned the semantics could be of upper or l
On Thu, 7 Jul 2016 20:08:40 +0200
Quentin Glidic wrote:
> On 07/07/2016 18:11, Emil Velikov wrote:
> > On 7 July 2016 at 10:05, Pekka Paalanen wrote:
> >>
> >> [snip]
> >>
> >> Now that you mentioned the semantics could be of upper or lower
> >> limit, the name should imply the meaning. I onl
On 8 July 2016 at 12:00, Quentin Glidic wrote:
> On 08/07/2016 12:52, Emil Velikov wrote:
>>
>> On 7 July 2016 at 19:08, Quentin Glidic
>> wrote:
>>>
>>> On 07/07/2016 18:11, Emil Velikov wrote:
On 7 July 2016 at 10:05, Pekka Paalanen wrote:
>
>
>
> [snip]
>>>
>>>
On 08/07/2016 13:00, Quentin Glidic wrote:
On 08/07/2016 12:52, Emil Velikov wrote:
On 7 July 2016 at 19:08, Quentin Glidic
wrote:
On 07/07/2016 18:11, Emil Velikov wrote:
On 7 July 2016 at 10:05, Pekka Paalanen wrote:
[snip]
Now that you mentioned the semantics could be of upper or
On 08/07/2016 12:52, Emil Velikov wrote:
On 7 July 2016 at 19:08, Quentin Glidic wrote:
On 07/07/2016 18:11, Emil Velikov wrote:
On 7 July 2016 at 10:05, Pekka Paalanen wrote:
[snip]
Now that you mentioned the semantics could be of upper or lower
limit, the name should imply the meani
On 7 July 2016 at 19:08, Quentin Glidic wrote:
> On 07/07/2016 18:11, Emil Velikov wrote:
>>
>> On 7 July 2016 at 10:05, Pekka Paalanen wrote:
>>>
>>>
>>> [snip]
>
>>>
>>> Now that you mentioned the semantics could be of upper or lower
>>> limit, the name should imply the meaning. I only thought
On 07/07/2016 18:11, Emil Velikov wrote:
On 7 July 2016 at 10:05, Pekka Paalanen wrote:
>> [snip]
Now that you mentioned the semantics could be of upper or lower
limit, the name should imply the meaning. I only thought of using
it as both lower limit (as in pkg-config check) *and* upper lim
On segunda-feira, 4 de julho de 2016 15:23:51 PDT Emil Velikov wrote:
> +Similar approach is used by ATK, QT and KDE programs/libraries,
Qt, with a lowercase t.
--
Thiago Macieira - thiago (AT) macieira.info - thiago (AT) kde.org
Software Architect - Intel Open Source Technology Center
_
On 7 July 2016 at 10:05, Pekka Paalanen wrote:
> On Wed, 6 Jul 2016 13:57:48 +0100
> Emil Velikov wrote:
>
>> On 5 July 2016 at 15:46, Pekka Paalanen wrote:
>> > On Mon, 4 Jul 2016 15:23:51 +0100
>> > Emil Velikov wrote:
>> >
>> >> From: Emil Velikov
>> >>
>> >> Signed-off-by: Emil Velikov
>
On Wed, 6 Jul 2016 13:57:48 +0100
Emil Velikov wrote:
> On 5 July 2016 at 15:46, Pekka Paalanen wrote:
> > On Mon, 4 Jul 2016 15:23:51 +0100
> > Emil Velikov wrote:
> >
> >> From: Emil Velikov
> >>
> >> Signed-off-by: Emil Velikov
> >> ---
> >> Pekka,
> >>
> >> There's a couple of things t
On 5 July 2016 at 15:46, Pekka Paalanen wrote:
> On Mon, 4 Jul 2016 15:23:51 +0100
> Emil Velikov wrote:
>
>> From: Emil Velikov
>>
>> Signed-off-by: Emil Velikov
>> ---
>> Pekka,
>>
>> There's a couple of things to 'break' - forward and backward
>> compatibility.
>>
>> Latter implies changing
On Mon, 4 Jul 2016 15:23:51 +0100
Emil Velikov wrote:
> From: Emil Velikov
>
> Signed-off-by: Emil Velikov
> ---
> Pekka,
>
> There's a couple of things to 'break' - forward and backward
> compatibility.
>
> Latter implies changing (removing) certain existing API, while the
> former is used
From: Emil Velikov
Signed-off-by: Emil Velikov
---
Pekka,
There's a couple of things to 'break' - forward and backward
compatibility.
Latter implies changing (removing) certain existing API, while the
former is used in reference to functionality introduced with minor
bumps.
Since people don't
13 matches
Mail list logo
