--nextPart1260489.JUeALeHDmq
Content-Type: text/plain;
  charset="utf-8"
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline


> I understand, but why don't we just all start using trunk? KDevelop
> requires only kdelibs trunk. KDEWebDev could also depend on trunk IMHO.

Because the risk that kdelibs is broken is higher and we have to fix kdeweb=
dev=20
after every breakage from kdelibs. It is just more convenient to have a=20
stable kdelibs for some time and not to work with a moving target. I mean=20
this is why it was created, right?

Jens

--nextPart1260489.JUeALeHDmq
Content-Type: application/pgp-signature

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

iD8DBQBEUkNMkYmIVB8IV+ARAp5dAKDCKJ7gthf/hmRB4orhfBtm7lcyagCfUkjy
BfTIGTnJlLs5PIJAT9UXKsQ=
=ljFU
-----END PGP SIGNATURE-----

--nextPart1260489.JUeALeHDmq--

_______________________________________________
KDevelop-devel mailing list
KDevelop-devel@barney.cs.uni-potsdam.de
http://barney.cs.uni-potsdam.de/mailman/listinfo/kdevelop-devel