Cc: duane_malcolm <d.malcolm AT auckland.ac.nz>, Unet <unet AT sourcemage.org>, Gareth Clay <gareth AT caffeinefuelled.co.uk>, vladimir_marek <vlmarek AT volny.cz>, Jeremy Blosser <jblosser AT sourcemage.org>, Pol Vinogradov <vin.public AT gmail.com>, SM-Commit Daemon <sm-commit AT lists.ibiblio.org>, Ladislav Hagara <ladislav.hagara AT unob.cz>, Andraž ruskie Levstik <ruskie AT mages.ath.cx>, Andrew Stitt <a AT t.armory.com>, Juuso Alasuutari <iuso AT sourcemage.org>, Treeve Jelbert <treeve01 AT pi.be>, Arjan Bouter <abouter AT gmail.com>, David Kowis <dkowis+smgl-p4 AT shlrm.org>, Ethan Grammatikidis <eekee AT eekee.is-a-geek.org>, Maurizio Boriani <baux AT member.fsf.org>
Subject: Re: [SM-Commit] PERFORCE change 76936 by Treeve Jelbert for review
Date: Tue, 28 Mar 2006 18:24:03 -0800
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Arwed von Merkatz wrote:
> On Tue, Mar 28, 2006 at 10:25:00PM +0100, Perforce Review Daemon wrote:
>> Change 76936 by treeve_jelbert@treeve-knowhow on 2006/03/28 22:22:22
>>
>> kde*-3.5.2 (part 1)
>
> If there's a part 2, shouldn't this stay in devel until the update is
> complete and then be integrated to test? I'm not familiar with the kde
> stack, does this work in a mixed environment? I'd guess so since it's
> only a micro version update, but you never know ...
I believe just kdelibs and kdebase (and arts, if people use it) need to
stay in sync, but I haven't tested this (and I'm assuming Treeve has,
since he uses KDE).