State diagram of patch status, possible bug in apps/patchwork/

Carl-Daniel Hailfinger c-d.hailfinger.devel.2006 at
Wed Jul 8 10:41:12 EST 2009


we're trying to use patchwork for the flashrom project (see and ) and there are some
obstacles which got in the way. I'll list them here in the hope you can
either fix them or tell me where to RTFM.

1. I could not find any documentation for patchwork, neither online nor
in the downloaded source code.

2. What's the expected or recomended patch lifecycle status diagram?
Will "Under review" automatically appear once the first Acked-by comment
happens? Having to extract logic from the application code is less than

3. apps/patchwork/ line 291 looks for the following regexp:
'^([Tt]ested|[Rr]eviewed|[Aa]cked|[Ss]igned-off|[Nn]acked)-by: .*$'
That regexp won't catch oddbal capitalizations like Signed-Off-by unless
I'm mistaken.

4. apps/patchwork/templatetags/ line 41ff is missing Nacked-by.

5. How can I automatically match commits against pending patches? We use
one centralized subversion repository and the mailing list gets a commit
mail for every commit. If matching committed patches automatically
against pending patches is not possible, can we have patchwork parse
replies to patches which usually say something like "...comitted in
r1234" or "thanks, r1234"?

6. Some parts of patchwork seem to hardcode git usage. Is that just
because nobody had the time to add subversion support as well?

7. Possible bug in the unarchive action in apps/patchwork/,
patch follows:

diff --git a/apps/patchwork/ b/apps/patchwork/
index 797951c..fa26aef 100644
--- a/apps/patchwork/
+++ b/apps/patchwork/
@@ -183,7 +183,7 @@ def set_patches(user, project, action, data, patches, context):
             str = 'archived'
         elif action == 'unarchive':
-            patch.archived = True
+            patch.archived = False
             str = 'un-archived'


More information about the Patchwork mailing list