From: Andrew Price <anprice@redhat.com> To: cluster-devel <cluster-devel@redhat.com> Cc: gfs2@lists.linux.dev Subject: [Cluster-devel] [ANNOUNCE] Goodbye cluster-devel, hello gfs2@lists.linux.dev Date: Tue, 29 Aug 2023 18:07:54 +0100 [thread overview] Message-ID: <9830d291-a86b-df63-0b03-c99c583609c8@redhat.com> (raw) Hi all, As cluster-devel is now only used for gfs2 and dlm development, we will be moving them to a new list hosted by kernel.org alongside other Linux subsystems' lists. The new list is gfs2@lists.linux.dev and it will be used for both gfs2 and dlm development. The Linux MAINTAINERS file and other references will be updated shortly to reflect the change. Information about the list hosting can be found here: https://subspace.kernel.org/lists.linux.dev.html To subscribe, send an email (the subject and body doesn't matter) to: Subscribe: gfs2+subscribe@lists.linux.dev Unsubscribe: gfs2+unsubscribe@lists.linux.dev If you prefer, the list can also be read via NNTP at: nntp://nntp.lore.kernel.org/dev.linux.lists.gfs2 The archives can be found here: https://lore.kernel.org/gfs2/ and filters can use the "List-Id: <gfs2.lists.linux.dev>" header. Thanks, Andy
WARNING: multiple messages have this Message-ID (diff)
From: Andrew Price <anprice@redhat.com> To: cluster-devel <cluster-devel@redhat.com> Cc: gfs2@lists.linux.dev Subject: [ANNOUNCE] Goodbye cluster-devel, hello gfs2@lists.linux.dev Date: Tue, 29 Aug 2023 18:07:54 +0100 [thread overview] Message-ID: <9830d291-a86b-df63-0b03-c99c583609c8@redhat.com> (raw) Hi all, As cluster-devel is now only used for gfs2 and dlm development, we will be moving them to a new list hosted by kernel.org alongside other Linux subsystems' lists. The new list is gfs2@lists.linux.dev and it will be used for both gfs2 and dlm development. The Linux MAINTAINERS file and other references will be updated shortly to reflect the change. Information about the list hosting can be found here: https://subspace.kernel.org/lists.linux.dev.html To subscribe, send an email (the subject and body doesn't matter) to: Subscribe: gfs2+subscribe@lists.linux.dev Unsubscribe: gfs2+unsubscribe@lists.linux.dev If you prefer, the list can also be read via NNTP at: nntp://nntp.lore.kernel.org/dev.linux.lists.gfs2 The archives can be found here: https://lore.kernel.org/gfs2/ and filters can use the "List-Id: <gfs2.lists.linux.dev>" header. Thanks, Andy
next reply other threads:[~2023-08-29 17:08 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2023-08-29 17:07 Andrew Price [this message] 2023-08-29 17:07 ` [ANNOUNCE] Goodbye cluster-devel, hello gfs2@lists.linux.dev Andrew Price 2023-09-06 8:36 ` Andrew Price 2023-09-06 8:36 ` [Cluster-devel] " Andrew Price
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=9830d291-a86b-df63-0b03-c99c583609c8@redhat.com \ --to=anprice@redhat.com \ --cc=cluster-devel@redhat.com \ --cc=gfs2@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: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes, see mirroring instructions on how to clone and mirror all data and code used by this external index.