Hi guys,
the three issues I have with patch work:
1.) No integration with testing (some machine could apply, build and run make
check before I do)
2.) Tracking of patches and not series (we seldomly want a single patch)
3.) No feedback if something has been applied
Now Intel[1] seems to have had some of the same concern because:
1.) Their patchwork has a "pull"/"stream" API to wait for changes and execute
them. It is in their manual. For us this means we need to somehow figure out
where the patch applies to. We can either have the discipline to put this into
the subject (git send-email can do it) or we try to see which repository has
the specific base commit. It also supports sending back mails with the patch
result.
2.) They track series now.
3.) This seems to be unsolved. But we can probably do something ourselves with
a little discipline (and in a how-to-contribute documentation). We can use the
Change-Id concept that is used by Gerrit. This is a simple local hook that adds
a "Change-Id: " line with a unique number.
so we will probably end up hosting our own patchwork and try to get intel
help/work on 3rd. Could we get a consensus how we know where to apply the patch
to?
kind regards
holger
[1]
http://damien.lespiau.name/2016/02/augmenting-mailing-lists-with-patchwork.html
