From: Lars Kurth <lars.kurth-LM2mM/qkH7s@public.gmane.org>
To: xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
"xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org"
<xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org>,
xen-japanese-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org,
xen-ia64-devel-GuqFBffKawufjV5vJvDCSg@public.gmane.org
Subject: Mailing list spring clean
Date: Tue, 08 Mar 2011 14:21:53 +0000 [thread overview]
Message-ID: <4D763B81.40504@xen.org> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1388 bytes --]
Hi everybody,
spring is coming, which is an excellent opportunity to retire old and
inactive mailing lists. Too many lists confuse users. If lists are not
active people may even get frustrated as they may not get an answer when
posting to the wrong list.
My proposal is to retire the mailing lists listed below, as they have
not been active for some time or get posts which should really be posted
in another list. We would retire lists in such a way that the lists are
deleted, but such that the archives are still available.
If you have any objections to the proposal, please fill out the
following form (http://xen.org/polls/mailinglist_springclean_2011.html)
by March 31st, <http://xen.org/polls/mailinglist_springclean_2011.html>
providing your name, e-mail and the mailing lists you want to keep and
press submit.
*Lists for projects which have completed some time ago:*
* Cloud-devel
* ova-devel
* xense-devel
* xen-smartio
* xen-ppc-devel
* xen-cim
*Lists that have become obsolete as discussions happen elsewhere
*(e.g. on blogs, other mailing lists or IRC)
* xen-announce
* xen-community
*Lists with a specific focus
*(e.g. in practice either xen-devel, xen-api or xen-users has been used
for these for some time)
* xen-tools
* xen-test
* xen-merge
* xm-test-devel
* xm-test-changelog
Best Regards
Lars
[-- Attachment #1.2: Type: text/html, Size: 20121 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
reply other threads:[~2011-03-08 14:21 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=4D763B81.40504@xen.org \
--to=lars.kurth-lm2mm/qkh7s@public.gmane.org \
--cc=xen-api-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-devel-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-ia64-devel-GuqFBffKawufjV5vJvDCSg@public.gmane.org \
--cc=xen-japanese-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.org \
--cc=xen-users-GuqFBffKawuULHF6PoxzQEEOCMrvLtNR@public.gmane.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 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.