All of lore.kernel.org
 help / color / mirror / Atom feed
From: Dominique Rousseau <d.rousseau@nnx.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: RE: So should we do anything?  (was Re: [Xen-announce] IMPORTANT: mailing lists moving)
Date: Thu, 17 Mar 2005 09:23:07 +0100	[thread overview]
Message-ID: <20050317082307.GX26748@nnx.com> (raw)
In-Reply-To: <A95E2296287EAD4EB592B5DEEFCE0E9D1E36DC@liverpoolst.ad.cl.cam.ac.uk>

Le Thu, Mar 17, 2005 at 07:53:49AM -0000, Ian Pratt [m+Ian.Pratt@cl.cam.ac.uk] a écrit:
> > Another interpretation is that we'll get auto-subscribed to the new
> > list but it will be non-transparent in the sense that a new list
> > password will be mailed to us, or maybe we'll lose digest settings,
> > or some other minor problem.
> 
> A couple of people have pointed out that it would be possible to do a
> bulk subscribe, but I'm not sure that this would be the 'polite' thing
> to do anyhow.

It takes only a few seconds to subscribe to the new list(s), and it will
help sorting out people who juste want the -user list and those that
want -devel.
And people have almost 2 weeks to do it, so I think bulk subscribe is
not necessary.


Dominique


-- 
Dominique Rousseau 
Neuronnexion, Prestataire Internet & Intranet
57, route de Paris 80000 Amiens
tel: 03 22 71 61 90 - fax: 03 22 71 61 99 - http://www.neuronnexion.fr


-------------------------------------------------------
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_ide95&alloc_id\x14396&op=click

      reply	other threads:[~2005-03-17  8:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-03-17  7:53 So should we do anything? (was Re: [Xen-announce] IMPORTANT: mailing lists moving) Ian Pratt
2005-03-17  8:23 ` Dominique Rousseau [this message]

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=20050317082307.GX26748@nnx.com \
    --to=d.rousseau@nnx.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.