Hi Ludo,
> The attached super-early-draft ‘guix review’ script fetches mboxes from > mumi—that part is OK. I like the idea! But, could we put this in mumi instead of guix? That way, other packages that use debbugs/mumi (skribilo comes to mind), can benefit from it as well. Something like $ guix shell mumi -- mumi review 54874 Maybe, we should read some config file, say mumi.scm, from the top-level directory of the current git repo to determine settings (think package name, debbugs/mumi web URI, post-processing function to provide feedback about the patch, etc.) specific to that repo. > What’s more difficult is the rest: determining what’s a patch and what’s > not (I gather this is something that b4 and Patchwork handle nicely), > getting the latest patch series, things like that. At some point, we should patch mumi to determine these. Determining the latest patch series shouldn't be hard if we use the Date header. guile-email will let us read any email header. WDYT? Cheers! Arun
