From: Tupshin Harper <tupshin@tupshin.com>
To: xen-devel@lists.sourceforge.net
Subject: Re: start xen-ia64-devel or just use xen-devel?
Date: Sun, 19 Dec 2004 15:41:20 -0800 [thread overview]
Message-ID: <cq53it$gc$1@sea.gmane.org> (raw)
In-Reply-To: <E1Cg8sN-0008E7-00@mta1.cl.cam.ac.uk>
Ian Pratt wrote:
>
>
> I think we probably need to create a xen-users list in addition
> to xen-devel. Assuming we do that, I don't see any reason not to
> hold the discussion on xen-devel (with private email as
> appropriate). Some of this stuff may be relevant to other ports
> anyhow.
>
> Ian
>
Speaking as somebody only interested in the x86 version and the x86_64
port, I agree with keeping various ports on the main list (at least for
now). The traffic is low enough that it is not burdensome, and it is
quite likely that the various ports will benefit from cross-polination
of discussions/ideas.
Starting a xen-users would also be good, since configuration and use
questions will rapidly become a larger portion of the whole.
-Tupshin
-------------------------------------------------------
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://productguide.itmanagersjournal.com/
next prev parent reply other threads:[~2004-12-19 23:41 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-12-19 17:39 start xen-ia64-devel or just use xen-devel? dan.magenheimer
2004-12-19 21:46 ` Ian Pratt
2004-12-19 23:41 ` Tupshin Harper [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-12-17 22:00 BAD gzip hdr on all 2.0 trees? Magenheimer, Dan (HP Labs Fort Collins)
2004-12-18 5:43 ` Andy Isaacson
2004-12-18 21:21 ` start xen-ia64-devel or just use xen-devel? dan.magenheimer
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='cq53it$gc$1@sea.gmane.org' \
--to=tupshin@tupshin.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.