From: Kyle Meyer <kyle@kyleam.com>
To: Pierre Neidhardt <mail@ambrevar.xyz>
Cc: help-guix@gnu.org
Subject: Re: Workflow with mu4e + magit for sending patchsets to guix?
Date: Mon, 30 Nov 2020 17:30:45 -0500 [thread overview]
Message-ID: <87k0u2lboq.fsf@kyleam.com> (raw)
In-Reply-To: <87k0u8v42a.fsf@ambrevar.xyz>
Pierre Neidhardt writes:
> --8<---------------cut here---------------start------------->8---
> (defvar ambrevar/known-mailing-list-archives
> '(("help-guix@gnu.org" . "guix-user")
> ("guix-devel@gnu.org" . "guix-devel")
> ("debbugs.gnu.org" . "guix-bugs"))
> "Alist of mail adresses and their Yhetil name.
[...]
Thanks.
> Note that I've set two entries, one that prefer guix-patches over
> guix-bugs because they seem to use the same recipient domain
Eric Wong has been working on adding an "external index" to public-inbox
that allows operating on a collection of inboxes.
https://public-inbox.org/meta/20201027075453.19163-1-e@80x24.org/
https://public-inbox.org/meta/20201126194543.GA30337@dcvr/
The feature is still being cooked, but I got around to trying it out
this weekend, and it seems to work nicely.
Anyway, that feature helps here because it allows all Guix-related lists
to be exposed under a single inbox. You can now construct a URL without
worrying about which particular list the message is from:
https://yhetil.org/guix/87k0u8v42a.fsf@ambrevar.xyz
next prev parent reply other threads:[~2020-11-30 22:31 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-16 20:28 Workflow with mu4e + magit for sending patchsets to guix? Christopher Lemmer Webber
2020-11-16 20:48 ` Christopher Baines
2020-11-16 23:49 ` zimoun
2020-11-17 2:36 ` Kyle Meyer
2020-11-17 7:28 ` Pierre Neidhardt
2020-11-17 14:10 ` zimoun
2020-11-25 9:19 ` Pierre Neidhardt
2020-11-25 12:33 ` zimoun
2020-11-26 9:51 ` Pierre Neidhardt
2020-11-30 22:30 ` Kyle Meyer [this message]
2020-12-01 9:10 ` Pierre Neidhardt
2020-12-01 16:26 ` zimoun
2020-11-17 15:01 ` zimoun
2020-11-18 4:55 ` Kyle Meyer
2020-11-18 8:17 ` zimoun
2020-11-17 15:39 ` Kyle Meyer
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=87k0u2lboq.fsf@kyleam.com \
--to=kyle@kyleam.com \
--cc=help-guix@gnu.org \
--cc=mail@ambrevar.xyz \
/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.
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).