The following bugs are blocking the next Amarok release:
This search was scheduled by bcooks...@kde.org.
Bug 302780:
https://bugs.kde.org/show_bug.cgi?id=302780
Priority: NOR Severity: normal Platform: Debian unstable
Assignee: amarok-bugs-d...@kde.org
Status: NEW
Summary: Whe
On Mon, Nov 19, 2012 at 09:11:18PM +0100, Matěj Laitl wrote:
> >
> > You have this restriction in StatSync::Provider, and according to
> > yourself.
I seem to have swallowed the end of the sentence. It should have gone
like this:
...according to yourself, existing QueryMakers won't work unless c
On 19. 11. 2012 Edward Hades Toroshchin wrote:
> On Sun, Nov 18, 2012 at 10:43:07PM -, Matěj Laitl wrote:
> > [wrt BlockingQueryMaker created from code in
> > StatSyncing::CollectionProvider]
> >
> > Cannot be done. There couldn't be any "BlockingQueryMaker only created
> > in the main thread"
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/107348/
---
(Updated Nov. 19, 2012, 3:18 p.m.)
Review request for Amarok and Myriam Sc
On 19. 11. 2012 Edward Hades Toroshchin wrote:
> Matěj Laitl wrote:
> > So, what's your "ready to be merged" opinion on this, Edward?
>
> I don't like it, but just go ahead, there doesn't seem to be anything that
> could be improved without improving all the rest of Amarok first.
Okay. I will for
On 19. 11. 2012 Lucas Lira Gomes wrote:
> as the only GSoC project that isn't yet fully finished, I believe that I
> owe you an explanation about its current status. I had worked a lot in it
> this weekend and got several things done.
Thumbs up!
> To begin with, Libtomahawk often slows down my pl
Hi Lucas,
On Mon, Nov 19, 2012 at 3:56 AM, Lucas Lira Gomes wrote:
> Hi everyone,
>
> as the only GSoC project that isn't yet fully finished, I believe that I owe
> you an explanation about its current status. I had worked a lot in it this
> weekend and got several things done.
>
> To begin with,
On Sun, Nov 18, 2012 at 10:43:07PM -, Matěj Laitl wrote:
> Cannot be done. There couldn't be any "BlockingQueryMaker only created
> in the main thread" restriction (which would make it useless) and
> without it, the code wouldn't work.
You have this restriction in StatSync::Provider, and accor
On Sun, Nov 18, 2012 at 10:30:11PM -, Matěj Laitl wrote:
> Well, the method is (and should only be) called by existing
> StatSyncing code
Then the existing code is the user of the API. The code exists, doesn't
mean it will stay unmodified for the rest of times.
> the "users" of the API would
> On Nov. 17, 2012, 7:59 p.m., Edward Hades Toroshchin wrote:
> > Haven't run it yet, but at least it compiles okay :)
>
> Matěj Laitl wrote:
> Thanks for the attentive review, I didn't expect somebody to dive that
> deep and I'm grateful.
>
> Matěj Laitl wrote:
> So, what's your "read
10 matches
Mail list logo
