On Wed, Mar 13, 2013 at 1:08 PM, Michael Pyne wrote:
> On Tuesday, March 12, 2013 20:38:30 Ben Cooksley wrote:
>> >> Does anyone have objections to the sysadmins realigning the 3 git
>> >> modules in
>> >> question? (And if so, I'd appreciate ideas for better ways to fix).
>> >
>> > Hi,
>> >
>> >
On Tuesday, March 12, 2013 20:38:30 Ben Cooksley wrote:
> >> Does anyone have objections to the sysadmins realigning the 3 git
> >> modules in
> >> question? (And if so, I'd appreciate ideas for better ways to fix).
> >
> > Hi,
> >
> > I would have no problem with moving kate.git around, splittin
Hi, you can find it at
http://techbase.kde.org/Schedules/KDE4/4.11_Release_Schedule
There are two main changes agreed by Release Team against the previous
releases:
* No specified time between Beta and RC tag and release. We will try to
release them ASAP after the tag to make them as useful as
Hi,
>> And the rest of the Python library API, like the stuff in Python/* and
>> Object/*?
> Those aren't being used. Only the parser is used.
I'm sorry, I forgot that the AST stuff is in Python/ (it has been a
while). So, the ast-related stuff from Python/ is being used too.
Thus, diffing Parser
On Tue, Mar 12, 2013 at 10:57 AM, Pino Toscano wrote:
> Hi,
>
> Alle sabato 9 marzo 2013, Sven Brauch ha scritto:
> > considering kdev-python is only using the Parser part of python, this
> > is actually all that has changed in the two years between 2.7.1 and
> > 2.7.3:
> > http://paste.kde.org/6
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109421/
---
(Updated March 11, 2013, 11:34 p.m.)
Review request for kdelibs and Jeremy
> On March 11, 2013, 5:19 a.m., Andrea Scarpino wrote:
> > "I was quite clear: "qmake" must point by default to Qt 4 if Qt 4 present."
> > While qtchooser sounds like a great solution to handle this, it only adds
> > more confusion from a packager view: we cannot have N differents
> > configura
> On March 11, 2013, 6:19 a.m., Andrea Scarpino wrote:
> > "I was quite clear: "qmake" must point by default to Qt 4 if Qt 4 present."
> > While qtchooser sounds like a great solution to handle this, it only adds
> > more confusion from a packager view: we cannot have N differents
> > configura
On Tuesday 12 March 2013 10:57:57 Pino Toscano wrote:
> Hi,
>
> Alle sabato 9 marzo 2013, Sven Brauch ha scritto:
> > considering kdev-python is only using the Parser part of python, this
> > is actually all that has changed in the two years between 2.7.1 and
> > 2.7.3:
> > http://paste.kde.org/69
Hi,
Alle sabato 9 marzo 2013, Sven Brauch ha scritto:
> considering kdev-python is only using the Parser part of python, this
> is actually all that has changed in the two years between 2.7.1 and
> 2.7.3:
> http://paste.kde.org/691184/
> As far as I can see, there's not a single change which would
On Saturday 09 March 2013 12:13:08 Pino Toscano wrote:
> Hi,
>
> Alle sabato 16 febbraio 2013, Sven Brauch ha scritto:
> > A while ago, I asked for a review of kdev-python, in order for it to
> > be moved from playground to extragear. There was some (legitimate)
> > objection about the fork of the
---
This is an automatically generated e-mail. To reply, visit:
http://git.reviewboard.kde.org/r/109282/#review29054
---
any comments? Otherwise I'm just going ahead and push it into m
Hi all,
On Mon, Mar 11, 2013 at 8:16 PM, Christoph Cullmann wrote:
>> Other alternatives include splitting kate up in the various
>> library/runtime-
>> support/application components but that's a lot of extra work for
>> what is
>> really just a kde-projects problem.
Just a note that we now hav
13 matches
Mail list logo
