[prev in list] [next in list] [prev in thread] [next in thread] 

List:       kwin
Subject:    Re: Re: Re: Re: Redesign kwin's kcm "All effects"
From:       Martin =?ISO-8859-1?Q?Gr=E4=DFlin?= <mgraesslin () kde ! org>
Date:       2012-03-29 5:50:24
Message-ID: 1632808.KqrtVnTbHS () martin-desktop
[Download RAW message or body]

[Attachment #2 (multipart/signed)]


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

["signature.asc" (application/pgp-signature)]

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


[prev in list] [next in list] [prev in thread] [next in thread]