From: Tobias Geerinckx-Rice <me@tobias.gr>
To: Christopher Baines <mail@cbaines.net>
Cc: Guix-devel <guix-devel@gnu.org>
Subject: Re: Patchwork + automated checking and testing of patches
Date: Wed, 31 Oct 2018 14:34:33 +0100 [thread overview]
Message-ID: <87y3ae5jod.fsf@tobias.gr> (raw)
In-Reply-To: <87h8h29z2j.fsf@cbaines.net>
Christopher,
Christopher Baines wrote:
> I've now written a very rough package and service for Patchwork
> [4], and
> managed to setup a instance here [5]. With the help of an email
> account
> subscribed to both guix-patches and guix-commits, getmail and a
> couple
> of scripts, it should also collect new patches sent to
> guix-patches, and
> mark those that have been merged to the master branch as
> "Accepted" [6].
>
> 4: https://debbugs.gnu.org/cgi/bugreport.cgi?bug=33185
> 5: https://patchwork.cbaines.net/
> 6:
> https://patchwork.cbaines.net/project/guix-patches/list/?state=3
Niiice. If that's ‘rough‘, I look forward to what's to come.
A lost battle, perhaps, but does Patchwork provide an option to
mangle e-mail addresses?
Kind regards,
T G-R
next prev parent reply other threads:[~2018-10-31 13:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-31 10:43 Patchwork + automated checking and testing of patches Christopher Baines
2018-10-31 13:34 ` Tobias Geerinckx-Rice [this message]
2018-10-31 13:53 ` Christopher Baines
2018-11-01 15:22 ` Ludovic Courtès
2018-11-01 18:55 ` Christopher Baines
2018-11-06 13:26 ` Ludovic Courtès
2018-11-06 15:13 ` Gábor Boskovits
2018-11-06 18:52 ` Ricardo Wurmus
2018-11-07 18:40 ` Christopher Baines
2018-11-07 22:00 ` Ludovic Courtès
2018-11-19 19:32 ` Christopher Baines
2018-11-22 9:07 ` Ludovic Courtès
2018-12-02 22:45 ` Chris Marusich
2018-12-03 0:51 ` Christopher Baines
2018-12-08 21:27 ` Chris Marusich
2019-02-01 12:53 ` Christopher Baines
2019-02-04 21:20 ` Ludovic Courtès
2019-02-08 12:04 ` Christopher Baines
2019-02-08 18:54 ` Björn Höfling
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=87y3ae5jod.fsf@tobias.gr \
--to=me@tobias.gr \
--cc=guix-devel@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).