--===============0776239970==
Content-Type: multipart/signed;
  boundary="nextPart6055354.R8aMEGfQc4";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart6055354.R8aMEGfQc4
Content-Type: text/plain;
  charset="iso-8859-2"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

On Wednesday 26 April 2006 08:02, Jens Herden wrote:
> Hi,
>
> I changed kdevquanta to use kdelibs from trunk because kdevelop also
> needs this.
> I do not really like this but I see no other solution in the moment.

What exactly did you need from KDevelop trunk? It is also possible to=20
update your (our) kdevelop from svn only when a new snapshot of kdelibs=20
comes out. Yes, we will have an older kdevelop and if we make local=20
modifications to it, it will be harder to put in svn, but it is=20
possible. Basicly we keep a local snapshot of kdevelop.

Andras

=2D-=20
Quanta Plus developer - http://quanta.kdewebdev.org
K Desktop Environment - http://www.kde.org

--nextPart6055354.R8aMEGfQc4
Content-Type: application/pgp-signature

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.2 (GNU/Linux)

iD8DBQBETxYXTQdfac6L/08RArBtAJ9Dpwfxr7vOQKyc++w69WAXynUcYACaA+P2
UKexoAia9W3gQlgvRcu/Lo0=
=1SHv
-----END PGP SIGNATURE-----

--nextPart6055354.R8aMEGfQc4--

--===============0776239970==
Content-Type: text/plain; charset="us-ascii"
MIME-Version: 1.0
Content-Transfer-Encoding: 7bit
Content-Disposition: inline

_______________________________________________
quanta-devel mailing list
quanta-devel@kde.org
https://mail.kde.org/mailman/listinfo/quanta-devel

--===============0776239970==--