Re: Review Request: Only show KSysguard & SystemSettings in menus when running KDE

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102038/ --- (Updated July 21, 2011, 10:39 p.m.) Review request for KDE Base Apps. Su

Re: Review Request: Only show KSysguard & SystemSettings in menus when running KDE

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102038/ --- (Updated July 21, 2011, 6:39 p.m.) Review request for KDE Base Apps. Sum

Re: Review Request: Only show KSysguard & SystemSettings in menus when running KDE

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102038/ --- (Updated July 21, 2011, 6:35 p.m.) Review request for KDE Base Apps. Sum

Re: Review Request: Only show KSysguard & SystemSettings in menus when running KDE

--- This is an automatically generated e-mail. To reply, visit: http://git.reviewboard.kde.org/r/102038/ --- (Updated July 21, 2011, 6:30 p.m.) Review request for KDE Base Apps. Sum

Re: Fixes in Git (first in stable, then merge to master)

Am 7/21/2011 23:22, schrieb Aurélien Gâteau: > What I have been doing recently to avoid cherry-picking is to create my > fixes in a separate work branch, then merge the branch in both 4.7 and > master branches. This way the commits do not have different commit ids. But this works only if you fork

Notification of repository rename - libkmap to libkgeomap

Hi all, As has been requested by a repository administrator, the repository "libkmap" on git.kde.org has been renamed to "libkgeomap". Those people with clones of this repository will need to adjust them in order to continue using them as follows: git remote set-url origin kde:libkgeomap Or: git

Re: Fixes in Git (first in stable, then merge to master)

Le 20/07/2011 11:52, Alex Fiestas a écrit : > Hi there > > Last few days I have been patching some pieces of our workspace here and > there, the first set of patches I did them directly into master which if > I remember correctly was against the policy. > So, the second round of fixes I tried to

Re: CDash of kdelibs

On Thursday 21 July 2011, Volker Krause wrote: > On Wednesday 20 July 2011 21:51:43 Alexander Neundorf wrote: > > Hi, > > > > Dave, if you find some time, could you please have a look at the issue > > here, whether it behaves as it should with using CTEST_USE_LAUNCHERS ? A > > link to a dashboard

Re: CDash of kdelibs

2011/7/20 Alexander Neundorf > Hi, > > Dave, if you find some time, could you please have a look at the issue > here, > whether it behaves as it should with using CTEST_USE_LAUNCHERS ? > A link to a dashboard before and the new one with the launchers are below. > > On Wednesday 20 July 2011, Rolf

Re: Review Request: Make mouse cursor size configurable

> On July 20, 2011, 2:46 p.m., Fredrik Höglund wrote: > > Lucas, first of all I want to say thank you for working on this. > > > > In good UI design it is important to think about the problem the user > > wants to solve from the user's point of view, and not in terms of how > > the underlying im

Re: Review Request: Make mouse cursor size configurable

> On July 12, 2011, 8:56 a.m., Christoph Feck wrote: > > kcontrol/input/xcursor/xcursortheme.cpp, line 73 > > > > > > Do you mean the sizes are always > 0, or do you mean the number of > > entries in the list is > 0

Re: CDash of kdelibs

On Wednesday 20 July 2011 21:51:43 Alexander Neundorf wrote: > Hi, > > Dave, if you find some time, could you please have a look at the issue here, > whether it behaves as it should with using CTEST_USE_LAUNCHERS ? > A link to a dashboard before and the new one with the launchers are below. > > O