Forward-ports in kde-workspace
Aaron J. Seigo
aseigo at kde.org
Mon Feb 7 05:41:35 GMT 2011
On Sunday, February 6, 2011, you wrote:
> Additionally, the following commit was partially backported (in
> r1214728); only the addLauncher call was changed, and not the
> connect/disconnect calls:
>
> commit 120064d95e890eeb8f748e641aa0c3ea13aef4c2
> Author: Aaron J. Seigo <aseigo at kde.org>
> Date: Sat Jan 15 23:11:15 2011 +0000
>
> don't supress the signal, just disconnect/connect to it
>
> svn path=/trunk/KDE/kdebase/workspace/; revision=1214696
the signals were removed in trunk/master; this is why the backport/forwardport
(whichever direction :) was different.
--
Aaron J. Seigo
humru othro a kohnu se
GPG Fingerprint: 8B8B 2209 0C6F 7C47 B1EA EE75 D6B7 2EB1 A7F1 DB43
KDE core developer sponsored by Qt Development Frameworks
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-core-devel/attachments/20110206/c00c3f2f/attachment.sig>
More information about the kde-core-devel
mailing list