--===============0686128774==
Content-Type: multipart/signed;
  boundary="nextPart1837932.2QRZ0uxEjY";
  protocol="application/pgp-signature";
  micalg=pgp-sha1
Content-Transfer-Encoding: 7bit

--nextPart1837932.2QRZ0uxEjY
Content-Type: Text/Plain;
  charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

On November 8, 2010 12:01:17 Ivan Cukic wrote:
> > * make the change shortly after the public release of 4.6, to maximize
> > the easy-backporting window
>=20
> Well, theoretically, we could do the backporting in a bit dirty way if we
> are careful - having the code in bot git repo and svn (in local) - where
> svn would be on a branch we want to backport to.
>=20
> At least I've got used to the .svn and .git setup (local .git until I
> finish something, then commit it to svn)
>=20

uhm... wouldn't git-svn be easier? :)

=2D-=20
Chani
http://chani.ca

--nextPart1837932.2QRZ0uxEjY
Content-Type: application/pgp-signature; name=signature.asc 
Content-Description: This is a digitally signed message part.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.12 (GNU/Linux)

iEYEABECAAYFAkzX3YIACgkQeGbAwpIS3Gyk3QCg4M0egetWUaEMzL9Ui3BMPSjS
UX0Aniny2WE0n4JlxpRR6rqmTJeCc09Z
=7ha1
-----END PGP SIGNATURE-----

--nextPart1837932.2QRZ0uxEjY--

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

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

--===============0686128774==--