On Tuesday 10 February 2015 14:48:51 Eike Hein wrote:
On 02/10/2015 01:30 PM, Sebastian Kügler wrote:
Without giving it much thought I would think either KI18n or Sonnet.
Or perhaps kcodecs, sounds like an encoding-related problem to me.
KCodecs was my first thought too, because:
*
On Feb. 1, 2015, 8:32 p.m., David Faure wrote:
-1 for not submitting this upstream for shared-mime-info.
I took care of it, it's committed, will be in s-m-i 1.4.
Milian Wolff wrote:
Could we add a comment to this file then, telling people to work on
upstream smi instead then?
See http://build.kde.org/job/kcodecs_master_qt5/83/changes
___
Kde-frameworks-devel mailing list
Kde-frameworks-devel@kde.org
https://mail.kde.org/mailman/listinfo/kde-frameworks-devel
On Saturday 14 February 2015 01:34:28 Matthew Dawson wrote:
Hi all,
If it is not too late to sneak an extra patch into KConfig's 5.7 release,
could commit 9eee15917e01a89d937d1cba2eebbe9d65daeb72 (
http://commits.kde.org/kconfig/9eee15917e01a89d937d1cba2eebbe9d65daeb72 ) be
added in?
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122499/#review76018
---
The real URL for the menu spec is
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122484/#review76016
---
Why not actually specify a context, for instance KCharsets?
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122498/#review76017
---
1) AFAICS KStartupInfo exists on all platforms nowadays, even
On 02/14/2015 11:49 AM, David Faure wrote:
And KGuiAddons would only be right if your code needed QtGui. But yeah that's
something to find out for sure - if a future implementation might need QtGui,
then the API should be in KGuiAddons from day one. This consideration makes it
hard to just say
On Saturday 14 February 2015 08:48:11 Matthew Dawson wrote:
On February 14, 2015 11:16:42 AM David Faure wrote:
This is rather a behavior-incompatible change (and another one to revert).
So, to avoid the packagers killing me for updating 5.7 two days *after*
the
supposed public release
On February 14, 2015 11:16:42 AM David Faure wrote:
This is rather a behavior-incompatible change (and another one to revert).
So, to avoid the packagers killing me for updating 5.7 two days *after* the
supposed public release day (*), I would rather make a 5.7.1 kconfig release
with this
Hi all,
As some of you will know, a couple of people have been working on
getting some patches integrated into QStandardPaths upstream in Qt, in
order to allow KDE applications and unit tests to be able to locate
their resources more easily on Windows and OSX. This would aid us both
in a
On Feb. 12, 2015, 11:49 p.m., Albert Astals Cid wrote:
Guy: ping?
pong! I was on the road until today
- Guy
---
This is an automatically generated e-mail. To reply, visit:
https://git.reviewboard.kde.org/r/122445/#review75949
12 matches
Mail list logo
