Hi Arne,
> $ cd path/to/guile && LANG=C guix shell mumi -- mumi search submitter:arne > is:open > > ERROR: In procedure open-file: > In procedure open-file: No such file or directory: > "path/to/guile/.mumi/config" There needs to be better error reporting here. I have registered a bug report. https://issues.guix.gnu.org/77591 >> 1. Applying a patch series locally > $ mumi current 72208 > 72208 [PATCH] doc: tour: note the top-level modules ice-9, scheme, and srfi > opened 9 months ago by Dr. Arne Babenhauserheide, last updated 5 months ago > $ mumi am > Applying: doc: tour: note the top-level modules ice-9, scheme, and srfi > > Looks like it pulled in too much from the email? I see you have sent this patch as an attachment. Unfortunately, `mumi am' only understands patches sent using `git send-email' (or `mumi send-email', which is a wrapper around `git send-email'). Patches improving the situation are welcome. >> 2. Send a multiple messages series > $ git format-patch --cover-letter HEAD^ -o my-patches > my-patches/0000-cover-letter.patch > my-patches/0001-doc-tour-note-the-top-level-modules-ice-9-scheme-and.patch > > (it feels like it may be nice not to venture into git here and instead > do something like mumi create-patches HEAD^ Possibly. But, is there anything special for `mumi create-patches' to do? Wouldn't it be a trivial wrapper around `git format-patch'? > I’m a bit afraid of calling mumi send-email, because I have no feeling > for what it will do. Will it honor the current issue? Yes, `mumi send-email' is a simple wrapper around `git send-email'. It merely calls `git send-email' with the right To and Cc addresses. And, yes, it will honor the current issue. It's reasonable to feel a bit afraid of invoking `mumi send-email'. I think, a --dry-run flag that makes `mumi send-email' print out the `git send-email' commands it will invoke, will help. I have registered an issue for this. https://issues.guix.gnu.org/77587 Thank you for the feedback, and have a nice weekend! Regards, Arun
