From: Nivedita Singhvi <niv@us.ibm.com>
To: Anthony Liguori <aliguori@us.ibm.com>
Cc: Michael Rice <michael@riceclan.org>,
Rik van Riel <riel@redhat.com>,
xen-devel@lists.sourceforge.net
Subject: Re: [Xen-announce] IMPORTANT: mailing lists moving
Date: Wed, 16 Mar 2005 09:48:03 -0800 [thread overview]
Message-ID: <42387153.1060404@us.ibm.com> (raw)
In-Reply-To: <423853A5.7090509@us.ibm.com>
Anthony Liguori wrote:
> Michael Rice wrote:
>
>> Subscribe everyone to both lists. It's sufficient because one can
>> easily unsub from either list at any time.
>>
>>
> I just subscribed to the new lists. It was completely painless and took
> less than 30 seconds. Not sure that doing a bulk subscribe and then
> asking folks to unsubscribe is really worth it.
Yep, it was as fast as unsubscribing - very painless.
Thanks to the Xensource Team.
The only suggestion I have is to make the default
"no" for the option of wanting copies of the email
to the list when you are already on the To: or Cc:
lists. Not sure why anyone would want the duplicates.
It's nice to be able to finally turn it off.
thanks,
Nivedita
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now.
http://ads.osdn.com/?ad_id=6595&alloc_id=14396&op=click
next prev parent reply other threads:[~2005-03-16 17:48 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-16 13:13 IMPORTANT: mailing lists moving Ian Pratt
2005-03-16 14:44 ` [Xen-announce] " Eric S. Johansson
2005-03-16 15:03 ` Rik van Riel
2005-03-16 15:30 ` Michael Rice
2005-03-16 15:41 ` Anthony Liguori
2005-03-16 16:02 ` Jerone Young
2005-03-17 7:13 ` Bastian Blank
2005-03-16 17:48 ` Nivedita Singhvi [this message]
2005-03-16 17:59 ` James Bulpin
2005-03-16 19:07 ` Rik van Riel
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=42387153.1060404@us.ibm.com \
--to=niv@us.ibm.com \
--cc=aliguori@us.ibm.com \
--cc=michael@riceclan.org \
--cc=riel@redhat.com \
--cc=xen-devel@lists.sourceforge.net \
/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.