- User Since
- Apr 2 2017, 12:03 PM (132 w, 6 d)
Thu, Oct 17
The 32px is a little bit fuzzy, but definitely betterthan what we have currently. I would say, go for it!
@astippich - the circle in the background is a very nice improvement!
Sat, Oct 12
Wed, Oct 9
Tue, Oct 8
Sun, Oct 6
Please do one change at a time.
Thu, Sep 26
Can you please provide an example which:
Sun, Sep 22
Sep 13 2019
Sep 10 2019
Solid should be quite fine. When queried for devices providing 'Solid::DeviceInterface::NetworkShare', it will only use the fstab backend, which does not block and only reparses fstab/mtab when these change.
Sep 7 2019
Aug 29 2019
I think it would be preferable to do this in KFM::PropertyInfo
Aug 24 2019
I think you end up with less code and duplication when you just merge the two existing jobs into one, and handle the fallback there.
Aug 23 2019
Aug 17 2019
Aug 16 2019
Please just return without message, and also change the one below.
Aug 8 2019
@poboiko - is the problem you describe purely theoretical, or did you actually see it happen?
Aug 7 2019
Jul 19 2019
Jul 17 2019
It tried to install the no longer existing DBus service file. Fixup pushed.
The correct fix is to check the returned/calculated ID in the IndexCleaner, otherwise its racy.
Jul 16 2019
I would have preferred this to only land when D22333 had been addressed fully, I assumed this required no further notice.
Jul 13 2019
This is inacceptable!
Jul 12 2019
Jul 11 2019
Why not just a singleshot timer from the constructor? Avoids any initial blocking ...
How do you guarantee *each thread local* copy now is connected to the right signals, i.e. the socket notifier for the mtab and inotify for fstab?
Jul 10 2019
Jul 8 2019
Jul 7 2019
Jul 6 2019
After having looked into the callchain again, I am not sure what the best action here is:
Jul 5 2019
Can I have a "go"?