Re: Mumi, public-inbox and tools

Hi! Ricardo Wurmus skribis: > Arun Isaac writes: > >> 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

Re: Mumi, public-inbox and tools

Arun Isaac writes: > 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

Re: Mumi, public-inbox and tools

Ludovic Courtès schreef op zo 08-05-2022 om 00:52 [+0200]: >    (info (N_ "downloaded ~a patch for issue #~a~%" > "downloaded ~a patches for issue #~a~%" For i18n, could positional arguments be used here?

Re: Mumi, public-inbox and tools

Hi Arun, On Sun, 08 May 2022 at 11:43, Arun Isaac wrote: > 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

Re: Mumi, public-inbox and tools

Hi, Really cool! On Sun, 08 May 2022 at 00:52, Ludovic Courtès wrote: > I think we could have, as a first step, a command that allows us to run: > > ./pre-inst-env guix review 54874 > > and that fetches patches, applies them, and ideally reports on the > difference and what needs to be

Re: Mumi, public-inbox and tools

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 $

Re: Mumi, public-inbox and tools

Hello! The attached super-early-draft ‘guix review’ script fetches mboxes from mumi—that part is OK. 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.

Re: Mumi, public-inbox and tools

Hi Arun, On Tue, 03 May 2022 at 23:20, Arun Isaac wrote: >> of public-inbox via yhetil.org/guix and the piem glue? > > I haven't thought carefully about public-inbox integration. But, if we > can do everything in mumi, do we need public-inbox at all? Well, some advantages I see after using a

Re: Mumi, public-inbox and tools

Hi zimoun, > WDYT? What is missing to bridge the current features of Mumi via > issues.guix.gnu.org, mumi indexes the full text and selected headers (the date, for example) of every email it receives. But, I don't know if it indexes the Message-ID header. If it does, then referring to emails

Mumi, public-inbox and tools

Hi, Recently, we discussed [1] in «public-inbox/elfeed -> Maildir bridge (was: Incentives for review)» some tips to ease the workflow dealing with the various lists and their volume. Kyle wrote some Emacs glue around public-inbox, named piem [2]. One cool feature exposed by Kyle in [1] is being