Re: New state for patches not complying with commit policy

[Koen Kooi <k.kooi@student.utwente.nl>]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On 23-01-10 13:19, Paul Menzel wrote:
> Am Samstag, den 23.01.2010, 11:42 +0100 schrieb Koen Kooi:
>> On 23-01-10 09:43, Holger Hans Peter Freyther wrote:
>>> right now I'm writing a Qt 4.6 based application that might help us
>> a bit with 
>>> the patchwork queue.
>>>
>>> The idea of the script is to have two things at the end:
>>>       1.) a branch with all the patches that applied and that can be published
>>>       2.) a list of patches that don't apply.
>>>
>>>
>>> What people are supposed to:
>>>
>>> 1.) Cherry pick from the branch
>>> 2.) Send updated patches, close the reports on patchwork...
>>
>> I think people that apply those patches to oe.dev should fix up the
>> commit message as well. The stack Khem pushed this week is just
>> awfull.
>>
>> I guess we should flag patches with bad commit messages as 'rejected' in
>> pw ASAP. We can weed out most of them by reject anything that lacks a
>> ':' in the subject line.
> 
> I am just getting into Patchwork [1][2], so I am sorry if I miss the
> obvious.
> 
> If it is possible, I suggest to add a new state (»Rejected – Commit
> Policy«) for patches not complying with the commit policy [3]?

We can add that easily, we did the same for the 'applied' state.

> As a bonus an automatically answer is sent to the message with the patch
> to the list with the following content, which is just a draft/suggestion
> of course.

I'm unsure if we can do that. Patchwork does support sending emails, but
I left it disabled since I suck at email stuff.
If someone knows how to make patchwork do that we can consider turning
such a feature on.

regards,

Koen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (Darwin)

iD8DBQFLWwNXMkyGM64RGpERAp59AJ476WIGYubuaxiqdmQ4yl4r+z2EWgCeOGqM
6D0qHrY1hvikflj9fpVLXAk=
=VKyT
-----END PGP SIGNATURE-----