From kwin  Thu Mar 29 05:50:24 2012
From: Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date: Thu, 29 Mar 2012 05:50:24 +0000
To: kwin
Subject: Re: Re: Re: Re: Redesign kwin's kcm "All effects"
Message-Id: <1632808.KqrtVnTbHS () martin-desktop>
X-MARC-Message: https://marc.info/?l=kwin&m=133300032829760
MIME-Version: 1
Content-Type: multipart/mixed; boundary="--===============8069298831365965703=="


--===============8069298831365965703==
Content-Type: multipart/signed; boundary="nextPart34182717.z6d1FYTQDg"; micalg="pgp-sha1"; protocol="application/pgp-signature"
Content-Transfer-Encoding: 7Bit


--nextPart34182717.z6d1FYTQDg
Content-Transfer-Encoding: 7Bit
Content-Type: text/plain; charset="utf-8"

On Wednesday 28 March 2012 16:18:39 Giorgos Tsiapaliwkas wrote:
> ok, I will prepare a sample.
> What name should I give to the branch?
> Also the how we will handle the patches? I prefer all the patches to go to
> the
> reviewboard and then to push them into the branch. ok?
Personally I would say use the workflow you want. Normally if a patch goes 
through reviewboard we can be sure that it made it in master. If it goes into 
a branch afterwards we lose the relationship "a closed review request is in 
master".

Cheers
Martin

--nextPart34182717.z6d1FYTQDg
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: This is a digitally signed message part.

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

iEYEABECAAYFAk9z+CAACgkQqVXwidMiVrpkAQCggKaACZycDozY9lHckrVZVVZ9
MHoAn1BqHjrIs7rFJeMs6LMflwxGoAoh
=uStj
-----END PGP SIGNATURE-----

--nextPart34182717.z6d1FYTQDg--


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

_______________________________________________
kwin mailing list
kwin@kde.org
https://mail.kde.org/mailman/listinfo/kwin

--===============8069298831365965703==--