> On 2010-11-29 22:24:15, John Layt wrote:
> > Before I get stuck in, three points:
> >
> > 1) Screenshots?
> > 2) API freeze: this will need explicit approval from the release team as
> > well as k-c-d. What's the feeling on this?
> > 3) String freeze: this will need an exemption for any new
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6014/#review9046
---
Before I get stuck in, three points:
1) Screenshots?
2) API freez
---
This is an automatically generated e-mail. To reply, visit:
http://svn.reviewboard.kde.org/r/6014/
---
Review request for kdelibs and KDE PIM.
Summary
---
For a very long tim
On Monday 29 November 2010 00:51:29 John Layt wrote:
> On Monday 29 November 2010 00:10:59 Albert Astals Cid wrote:
> > A Dilluns, 29 de novembre de 2010, Christoph Feck va escriure:
> > > Hi,
> > >
> > > kdereview contains two new modules, but I did not see the announcement
> > > here. libkmap pr
On Wednesday 29 September 2010, Anders Lund wrote:
> Kate uses kdepimlibs to get the name and email of the user for template
> expansion.
Why doesn't it use kio's KEmailSettings, for this rather simple need?
kmail/kdepimlibs sets the data in kemailsettings, so it should work out of the
box for
On Monday 09 August 2010, Volker Krause wrote:
> On Saturday 07 August 2010 02:24:16 Aaron J. Seigo wrote:
> > On August 6, 2010, Thiago Macieira wrote:
> > > Side comment: shouldn't all of this (the includes and the installation
> > > rules) be auto-generated?
> >
> > they should, but as you poin
> Heya folks :)
>
> toma is awesome and because he's awesome he created
> http://www.kde.org/releaseschedule.ics after I asked him to. We've had
> ics files for each cycle already but you'd need to subscribe to the
> new one each cycle. This one now combines them all and you can
> subscribe to it i
> On 2010-11-29 00:08:22, Albert Astals Cid wrote:
> > Why did you change the if/else logic? Also you added another kError when
> > there was an existing one already.
> >
> > Also as commented on IRC maybe it would make sense to emit a signal to warn
> > whoever might be interested that an err
