From: Ricardo Wurmus <rekado@elephly.net>
To: Christopher Baines <mail@cbaines.net>
Cc: guix-devel@gnu.org, guix-maintainers@gnu.org
Subject: Re: Project direction with testing changes (branches and patches)
Date: Tue, 10 Aug 2021 09:05:54 +0200 [thread overview]
Message-ID: <87czqllqy5.fsf@elephly.net> (raw)
In-Reply-To: <87r1f2i82z.fsf@cbaines.net>
Christopher Baines <mail@cbaines.net> writes:
> I think using Patchwork or Mumi is viable, it would probably not
> be
> great to use both in the long term. The most useful thing for me
> would
> be to pick an approach.
>
> Patchwork is closer in terms of features I think, since it has
> an API
> for patch series and checks. I know mumi gained the ability to
> generate
> mbox files for patch series now though.
I wouldn’t mind getting rid of Mumi.
Surely Patchwork has a way to configure the user interface
somewhat?
> I think the requirements in terms of Mumi would be to have some
> way of
> querying for patch series to test, or at least all/recent patch
> series. I suppose something could just ask for the 1st or latest
> series
> each time there's an email to a issue, that might be the
> simplest
> approach.
There is an /issue/<id>/patch-set/<num> handler to download patch
series. IIRC there is a bug somewhere that makes it not work as
intended, but I did use it in the past to get a whole bunch of
patches and apply them with ‘git am’.
> Then there's the bits you describe about showing relevant
> information about whatever tests take place. I guess Mumi would
> need an
> API or some way to find out about that information, and then
> display
> it. Maybe that could happen in the form of emails with
> machine+human
> readable data that Mumi could interpret.
I don’t know what this means. What exactly is needed here?
> Unfortunately I don't know much about the Mumi
> internals. Ricardo, are
> you able to comment on the feasibility and whether this
> direction would
> make sense?
I think it’s feasible to add a few more things to Mumi to make the
existing features work better. But I should also emphasize that
I’m in no way attached to Mumi. If we have something better I’d
be happy to retire it. Mumi has served us well; we don’t need to
extend its use beyond what is reasonable.
--
Ricardo
next prev parent reply other threads:[~2021-08-10 7:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-01 11:50 Project direction with testing changes (branches and patches) Christopher Baines
2021-08-04 21:15 ` Ludovic Courtès
2021-08-09 22:09 ` Christopher Baines
2021-08-10 6:04 ` Mathieu Othacehe
2021-08-10 19:26 ` Christopher Baines
2021-08-11 10:37 ` Ludovic Courtès
2021-08-11 22:27 ` Christopher Baines
2021-08-10 7:05 ` Ricardo Wurmus [this message]
2021-08-12 8:04 ` Lars-Dominik Braun
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
List information: https://guix.gnu.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87czqllqy5.fsf@elephly.net \
--to=rekado@elephly.net \
--cc=guix-devel@gnu.org \
--cc=guix-maintainers@gnu.org \
--cc=mail@cbaines.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 public inbox
https://git.savannah.gnu.org/cgit/guix.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).