From: Thomas Schwinge <thomas@schwinge.name>
To: overseers@sourceware.org
Cc: crossgcc-owner@gcc.gnu.org, crossgcc-owner@sourceware.org
Subject: sourceware.org migration: 'crossgcc' mailing list
Date: Tue, 10 Mar 2020 17:12:22 +0100 [thread overview]
Message-ID: <87pndk89zt.fsf@euler.schwinge.homeip.net> (raw)
[-- Attachment #1: Type: text/plain, Size: 674 bytes --]
Hi!
First, thanks for you work on the sourceware.org migration!
I just wanted to report that upon reviewing my current subscriptions, I
noticed that I'm still subscribed to the 'crossgcc' mailing list --
haven't used that in ages. ;-)
..., but more importantly, that 'crossgcc' used to be hosted at
sourceware.org ezmlm, but is now hosted at gcc.gnu.org Mailman. Despite
its name, it's not really tied to GCC, so maybe it's appropriate to move
it back to sourceware.org? (I don't have any strong opinion myself.)
I have not tried whether posting to <crossgcc@sourceware.org> still
works, or only <crossgcc@gcc.gnu.org> now works.
Grüße
Thomas
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 658 bytes --]
reply other threads:[~2020-03-10 16:12 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=87pndk89zt.fsf@euler.schwinge.homeip.net \
--to=thomas@schwinge.name \
--cc=crossgcc-owner@gcc.gnu.org \
--cc=crossgcc-owner@sourceware.org \
--cc=overseers@sourceware.org \
/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).