On Tue, Mar 28, 2017 at 5:21 AM, Matthieu Gallien <
gallien.matth...@gmail.com> wrote:
> Hello all,
>
> Sorry to exhume this old thread, but
>
> Is there a common agreement on the best path forward for Baloo versus
> the current situation ?
>
> I have an interest in having a global KDE solution wh
Hello all,
Sorry to exhume this old thread, but
2016-12-29 13:47 GMT+01:00 Dominik Haumann :
> Hi all,
>
> CC: plasma-devel, due to stability issues
>
> On Fri, Oct 7, 2016 at 5:56 PM, Christoph Cullmann
> wrote:
>> Hi,
>>
> [...]
>> Actually, the bugs.kde.org page tells you the facts: The bug
Hi all,
CC: plasma-devel, due to stability issues
On Fri, Oct 7, 2016 at 5:56 PM, Christoph Cullmann wrote:
> Hi,
>
[...]
> Actually, the bugs.kde.org page tells you the facts: The bug number
> was constant increasing since > 1 year. The thread lists some other facts
> what is wrong ATM and shou
On Sun, Oct 16, 2016 at 2:16 PM, Christoph Cullmann wrote:
> Hi,
>
> (evil top posting)
>
> given the silence, I assume any interest in baloo has stopped once more, or?
> Or are there any plans how to fixup the current situation?
I'm not going to be very involved with this.
I've already expresse
On Fri, Oct 7, 2016 at 8:08 PM, Christoph Cullmann wrote:
>
> I did experiments and search works with tracker, but yes, a problem is
> tagging,+
> which ATM doesn't work. Nor do I say that is a ready solution now, just a
> possibility
> to avoid having to maintain low level code with at most 1 p
Hi,
Unfortunately I've been hit my multiple pretty severe health scares in the
last month, and have no idea when I'm going to be at 100% again.
For the time being I'd rather not hold up any development, so don't hold
back anything on my account.
-- Boudhayan
On 16 October 2016 at 17:46, Christo
Hi,
(evil top posting)
given the silence, I assume any interest in baloo has stopped once more, or?
Or are there any plans how to fixup the current situation?
Greetings
Christoph
- Am 7. Okt 2016 um 20:08 schrieb cullmann cullm...@absint.com:
> Hi,
>
>> Hey
>>
>> On Fri, Oct 7, 2016 at 6
Hey
On Fri, Oct 7, 2016 at 6:34 PM, Christoph Cullmann wrote:
> Hi,
>
>> On Fri, Oct 7, 2016 at 5:58 PM, Christoph Cullmann
>> wrote:
>>>
>
> 1) No handling of DB errors beside asserting
> 2) No handling of errors in the extractors (e.g. see the fixes I did, all
> extractors will need more of
Hi,
> Hey
>
> On Fri, Oct 7, 2016 at 6:34 PM, Christoph Cullmann
> wrote:
>> Hi,
>>
>>> On Fri, Oct 7, 2016 at 5:58 PM, Christoph Cullmann
>>> wrote:
>>
>> 1) No handling of DB errors beside asserting
>> 2) No handling of errors in the extractors (e.g. see the fixes I did, all
>> extract
On Fri, Oct 7, 2016 at 6:20 PM, Aleix Pol wrote:
>>>
>>
>> I don't understand why all framework discussions must happen on the
>> same list. It just adds to a crazy amount of noise, which one then
>> needs to parse through.
>
> Arguing that it should be elsewhere because you'd like to ignore the
>
On Fri, Oct 7, 2016 at 6:14 PM, Christoph Cullmann wrote:
>>>
>>
>> I don't understand why all framework discussions must happen on the
>> same list. It just adds to a crazy amount of noise, which one then
>> needs to parse through.
>
> If you would have baloo-devel I could understand that point,
vel"
>> Gesendet: Freitag, 7. Oktober 2016 17:56:35
>> Betreff: Re: Scrap Baloo Thread Feedback
>>
>> Hi,
>>
>>> Hey guys
>>>
>>> I was told there is a thread about scrapping Baloo. All Baloo
>>> discussion used to happen on kde-de
On Friday, 7 October 2016 18:27:30 CEST Vishesh Handa wrote:
> On Fri, Oct 7, 2016 at 6:20 PM, Aleix Pol wrote:
> >> I don't understand why all framework discussions must happen on the
> >> same list. It just adds to a crazy amount of noise, which one then
> >> needs to parse through.
> >
> > Arg
On Fri, Oct 7, 2016 at 6:01 PM, Vishesh Handa wrote:
> On Fri, Oct 7, 2016 at 5:57 PM, Kevin Funk wrote:
>> On Friday, 7 October 2016 17:24:26 CEST Vishesh Handa wrote:
>>> Hey guys
>>>
>>> I was told there is a thread about scrapping Baloo. All Baloo
>>> discussion used to happen on kde-devel an
Hi,
> On Fri, Oct 7, 2016 at 6:14 PM, Christoph Cullmann
> wrote:
>>>
>>> I don't understand why all framework discussions must happen on the
>>> same list. It just adds to a crazy amount of noise, which one then
>>> needs to parse through.
>>
>> If you would have baloo-devel I could unders
Hi,
> On Fri, Oct 7, 2016 at 5:57 PM, Kevin Funk wrote:
>> On Friday, 7 October 2016 17:24:26 CEST Vishesh Handa wrote:
>>> Hey guys
>>>
>>> I was told there is a thread about scrapping Baloo. All Baloo
>>> discussion used to happen on kde-devel and that's where the review
>>> requests go. It's t
On Fri, Oct 7, 2016 at 5:57 PM, Kevin Funk wrote:
> On Friday, 7 October 2016 17:24:26 CEST Vishesh Handa wrote:
>> Hey guys
>>
>> I was told there is a thread about scrapping Baloo. All Baloo
>> discussion used to happen on kde-devel and that's where the review
>> requests go. It's the only reaso
On Friday, 7 October 2016 17:24:26 CEST Vishesh Handa wrote:
> Hey guys
>
> I was told there is a thread about scrapping Baloo. All Baloo
> discussion used to happen on kde-devel and that's where the review
> requests go. It's the only reason I am still subscribed to kde-devel.
Heya,
Baloo is a
Hi,
> Hey guys
>
> I was told there is a thread about scrapping Baloo. All Baloo
> discussion used to happen on kde-devel and that's where the review
> requests go. It's the only reason I am still subscribed to kde-devel.
That is nice, but given baloo is a framework, that was unexpected, sorry.
Hey guys
I was told there is a thread about scrapping Baloo. All Baloo
discussion used to happen on kde-devel and that's where the review
requests go. It's the only reason I am still subscribed to kde-devel.
I must say, the thread is overall quite disappointing. There seems to
be no scientific or
20 matches
Mail list logo
