On mardi 6 juin 2017 13:58:35 CEST Harald Sitter wrote:
> On Sat, Jun 3, 2017 at 11:32 AM, David Faure wrote:
> > On mardi 30 mai 2017 16:18:42 CEST Aleix Pol wrote:
> >> On Tue, May 30, 2017 at 4:10 PM, Luigi Toscano
> >
> > wrote:
> >> > On Tuesday, 30
On Sat, Jun 3, 2017 at 11:32 AM, David Faure wrote:
> On mardi 30 mai 2017 16:18:42 CEST Aleix Pol wrote:
>> On Tue, May 30, 2017 at 4:10 PM, Luigi Toscano
> wrote:
>> > On Tuesday, 30 May 2017 16:06:56 CEST Harald Sitter wrote:
>> >> Is there a reason
On mardi 30 mai 2017 16:18:42 CEST Aleix Pol wrote:
> On Tue, May 30, 2017 at 4:10 PM, Luigi Toscano
wrote:
> > On Tuesday, 30 May 2017 16:06:56 CEST Harald Sitter wrote:
> >> Is there a reason ECM's project is placed in kdesupport rather than
> >> frameworks?
> >>
>
On Tue, May 30, 2017 at 4:10 PM, Luigi Toscano wrote:
> On Tuesday, 30 May 2017 16:06:56 CEST Harald Sitter wrote:
>> Is there a reason ECM's project is placed in kdesupport rather than
>> frameworks?
>>
>>
On Tuesday, 30 May 2017 16:06:56 CEST Harald Sitter wrote:
> Is there a reason ECM's project is placed in kdesupport rather than
> frameworks?
>
> https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects/kdesupport/ext
> ra-cmake-modules
>
> Seems a bit fishy at best and practically means
Is there a reason ECM's project is placed in kdesupport rather than frameworks?
https://cgit.kde.org/sysadmin/repo-metadata.git/tree/projects/kdesupport/extra-cmake-modules
Seems a bit fishy at best and practically means that if ECM ever were
to get translations it wouldn't inherit