2012/2/19 Ben Cooksley :
>
> First, our hooks are in python - so any changes would need to be in Python
> as well.
I can speak a bit of python, would be a nice way for learning more :)
>
> Second, there is a legitimate use for pushing merge commits - namely
> integrating a seperate remote branch.
On Sunday 19 February 2012, Stephen Kelly wrote:
> Alexander Neundorf wrote:
...
> > KF5 package, as small as it may be. A library containing only a function
> > which returns the version, or something like this.
> > Depending on this small (header only ?)
>
> It would have to be compiled in proba
Alexander Neundorf wrote:
> On Saturday 18 February 2012, Kevin Ottens wrote:
>> On Saturday 18 February 2012 18:13:00 Alexander Neundorf wrote:
>> > On Saturday 18 February 2012, Kevin Ottens wrote:
>> > > So the other possibility would be to have the version number in the
>> > > main CMakeLists.
2012/2/19 Stephen Kelly :
> Stephen Kelly wrote:
>
>>
>> Hi there,
>>
>> I was reviewing the changes in the frameworks branch from yesterday.
>> Something I noticed was that there are a lot of merge commits that don't
>> need to exist.
>
> Ugh. Yet more of this just appeared... Recent history in th
hi all...
there is a new library in staging: libkwindowsystem
it pulls in kdeui/windowmanagement/ and Plasma::WindowEffects as well as a few
x11 helper classes from kdeui.
these helper classes are public API in Platform 4.x but are only used by the
classes in libkwindowsystem. as such i've mad
Alexander Neundorf wrote:
> If some library needs some exotic library, it should be good enough if it
> contains the Find-module itself.
This wasn't on the wiki page. I added it with the recommendation that such
find modules shouldn't be installed.
__
