From: zimoun <zimon.toutoune@gmail.com>
To: "Ludovic Courtès" <ludo@gnu.org>,
"Arun Isaac" <arunisaac@systemreboot.net>
Cc: Guix Devel <guix-devel@gnu.org>, Kyle Meyer <kyle@kyleam.com>,
Ricardo Wurmus <rekado@elephly.net>
Subject: Re: Mumi, public-inbox and tools
Date: Sun, 08 May 2022 22:29:29 +0200 [thread overview]
Message-ID: <86ilqf6a52.fsf@gmail.com> (raw)
In-Reply-To: <87a6btymzz.fsf@gnu.org>
Hi,
Really cool!
On Sun, 08 May 2022 at 00:52, Ludovic Courtès <ludo@gnu.org> 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 built.
Currently, using the hhtps://yhetil.org/guix public-inbox instance,
coupled to the Emacs package ’piem’, I already have that. :-)
Basically, I use Emacs code from emacs-debbugs to query, then the Emacs
package ’piem’ [1] coupled [2] to the Python tool ’b4’ [3] and done.
Well, maybe using Scheme code for query Debbugs via Mumi, then instead
of,
> (define (apply-patch patch)
> (invoke "git" "am" "-s" patch))
’invoke’ the B4 tool. Other said, start to move all the hard work of
extracting the patches and application to an external tool and just glue
with Scheme (instead of Emacs lisp as ’piem’, for instance).
Then this Python B4 could be reimplemented (or adapted) using Scheme.
1: <https://docs.kyleam.com/piem/>
2: <https://docs.kyleam.com/piem/Applying-patches.html>
3: <https://git.kernel.org/pub/scm/utils/b4/b4.git>
Cheers,
simon
next prev parent reply other threads:[~2022-05-08 20:41 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-02 18:10 Mumi, public-inbox and tools zimoun
2022-05-03 17:50 ` Arun Isaac
2022-05-04 8:53 ` zimoun
2022-05-07 22:52 ` Ludovic Courtès
2022-05-08 6:13 ` Arun Isaac
2022-05-08 20:59 ` zimoun
2022-05-08 21:07 ` Ricardo Wurmus
2022-05-15 21:08 ` Ludovic Courtès
2022-05-08 20:29 ` zimoun [this message]
2022-05-09 16:56 ` Maxime Devos
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86ilqf6a52.fsf@gmail.com \
--to=zimon.toutoune@gmail.com \
--cc=arunisaac@systemreboot.net \
--cc=guix-devel@gnu.org \
--cc=kyle@kyleam.com \
--cc=ludo@gnu.org \
--cc=rekado@elephly.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/guix.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.