Cyril Roelandt <tipec...@gmail.com> skribis: > Well, I wanted to have automatic reviews for certain patches, so I wrote > a quick and dirty piece of Python code that, given an email, extracts a > patch from it, applies it on top of master, and runs "make" and "guix > lint <pkg>". > > The idea was to use offlineimap to check my guix directory on a regular > basis, and inotify to trigger the Python code whenever a new mail was > fetched.
Nice! > In the end, it is a bit more complex than what I thought, because there > are lots of ways to send a patch: there are different possible > encodings, one might send a patch attached to an email, or attach a > patch generated using git format-patch, or use git send-email... Also, > the code I wrote is Guix-centric, and it might be nice to have an > agnostic tool instead. Well, not a problem for us. ;-) > I think patchwork[1] does a nice job of keeping track of threads in > mailing-lists (which my tool cannot do at the moment), but I don't know > if it can trigger a CI build. Also, Qemu seems to have some sort of > email-based CI, but I am not sure what version is the "right" one (there > are forks at https://github.com/aliguori/patches, > https://github.com/stefanha/patches/tree/stefanha-tweaks and probably > some other places). There is also https://github.com/famz/patchew, but > it seems to require Docker... I head good stuff about QEMU’s ‘patches’ thing (it also has an Emacs interface IIRC.) If somebody is interested in it, it would be great to set it up for Guix. Thanks, Ludo’.
