From: Mekeor Melire <mekeor@posteo.de>
To: zimoun <zimon.toutoune@gmail.com>
Cc: help-guix@gnu.org
Subject: Re: This is how you import a mailing list archives (e.g. guix-patches) into mu4e
Date: Wed, 07 Dec 2022 02:27:24 +0000 [thread overview]
Message-ID: <87sfhskkry.fsf@posteo.de> (raw)
In-Reply-To: <86a640kbqg.fsf@gmail.com>
2022-12-06 12:33 zimon.toutoune@gmail.com:
> On Mon, 05 Dec 2022 at 21:43, Mekeor Melire <mekeor@posteo.de> wrote:
>
> > I guess, a disadvantage of using public-inbox is that it's not an
> > official service of the GNU Guix community.
>
> It is up to us to have an “official” instance. :-) Well, I remember
> discussing how to setup a public-inbox instance for Guix but I fail to
> find the message (probably a discussion on guix-sysadmin@gnu.org :-)).
>
> I mean the Guix project already serves https://issues.guix.gnu.org which
> is an improvement, IMHO, over https://bugs.gnu.org. We could also have
> https://lists.guix.gnu.org serving ’public-inbox’es for the various
> Guix mailing lists.
Yes, it'd be lovely if there were official GNU Guix public-inboxes, I
agree. Personally, I just started to use yhetil.org as of today, for my
local copy of the mailing-lists. But it'd be much nicer to rely on an
official service. I should go and find that old thread in the
guix-sysadmin list.
next prev parent reply other threads:[~2022-12-07 2:31 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-16 23:04 This is how you import a mailing list archives (e.g. guix-patches) into mu4e Mekeor Melire
2022-11-16 23:22 ` jbranso
2022-11-16 23:41 ` Mekeor Melire
2022-12-04 20:16 ` Mekeor Melire
2022-12-05 15:39 ` Joshua Branson
2022-12-05 8:45 ` zimoun
2022-12-05 21:43 ` Mekeor Melire
2022-12-06 11:33 ` zimoun
2022-12-07 2:27 ` Mekeor Melire [this message]
2022-12-07 10:33 ` zimoun
2022-12-06 1:03 ` Kyle Meyer
2022-12-06 12:03 ` zimoun
2022-12-07 2:02 ` Kyle Meyer
2022-12-07 10:38 ` zimoun
2022-12-07 2:19 ` Mekeor Melire
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=87sfhskkry.fsf@posteo.de \
--to=mekeor@posteo.de \
--cc=help-guix@gnu.org \
--cc=zimon.toutoune@gmail.com \
/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).