distributions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Guillem Jover <guillem@debian.org>
To: distributions@lists.linux.dev
Cc: distributions@lists.freedesktop.org
Subject: Distributions coordination lists
Date: Thu, 16 Feb 2023 02:39:44 +0100	[thread overview]
Message-ID: <Y+2JYG5pYyyG1CG0@thunder.hadrons.org> (raw)

Hi!

I just noticed this new distributions coordination list:

  https://subspace.kernel.org/lists.linux.dev.html

Which seems to have already close to 80 participants. Although there
was already a list that seems had the exact same purpose at:

  https://lists.freedesktop.org/mailman/listinfo/distributions

With around 280 participants. I think it would be nice to avoid
fragmentation for this kind of coordination efforts?

(In any case I've subscribed to the new list too for now.)

Thanks,
Guillem

             reply	other threads:[~2023-02-16  1:39 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-16  1:39 Guillem Jover [this message]
2023-02-16  7:06 ` Distributions coordination lists Dan Čermák
2023-03-08 23:33   ` Sam James
2023-03-08 23:40     ` Neal Gompa
2023-02-16 16:16 ` Mats Wichmann

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=Y+2JYG5pYyyG1CG0@thunder.hadrons.org \
    --to=guillem@debian.org \
    --cc=distributions@lists.freedesktop.org \
    --cc=distributions@lists.linux.dev \
    /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).