From: Chris Gianelloni <wolf31o2@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] Virtualization Herd
Date: Wed, 05 Jul 2006 08:48:43 -0400 [thread overview]
Message-ID: <1152103724.21775.12.camel@cgianelloni.nuvox.net> (raw)
In-Reply-To: <1151975355.21600.12.camel@athena.fprintf.net>
[-- Attachment #1: Type: text/plain, Size: 832 bytes --]
On Mon, 2006-07-03 at 21:09 -0400, Daniel Gryniewicz wrote:
> I'm open to arguments in favor of such a project, tho, if people have
> real plans. Certainly, an easier way to generate and maintain root
> filesystems for UML would be nice.
As far as VMware is concerned, I see no point in this herd. All of the
VMware stuff is already managed by the VMware team, and is a part of the
vmware herd. Adding it to a broader herd won't improve VMware in any
way. The only thing it will do is ensure that the members of the VMware
team get emails about bugs in things they aren't interested in working
with, or have no knowledge of whatsoever.
If such a herd does form, leave VMware out of it, please.
--
Chris Gianelloni
Release Engineering - Strategic Lead
x86 Architecture Team
Games - Developer
Gentoo Linux
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-07-05 12:58 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-03 17:49 [gentoo-dev] Virtualization Herd Nick Devito
2006-07-03 19:48 ` Benedikt Böhm
2006-07-03 19:56 ` Nick Devito
2006-07-03 20:28 ` Benedikt Böhm
2006-07-03 20:38 ` Benedikt Böhm
2006-07-03 21:18 ` Nick Devito
2006-07-04 1:09 ` Daniel Gryniewicz
2006-07-04 2:15 ` Nick Devito
2006-07-04 3:03 ` Daniel Gryniewicz
2006-07-05 12:48 ` Chris Gianelloni [this message]
2006-07-05 15:40 ` Benedikt Böhm
2006-07-04 11:11 ` Chris Bainbridge
2006-07-04 13:59 ` Nick Devito
2006-07-04 14:27 ` Ned Ludd
2006-07-04 20:00 ` Kevin F. Quinn
2006-07-04 20:08 ` Kevin F. Quinn
2006-07-05 12:56 ` Chris Gianelloni
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=1152103724.21775.12.camel@cgianelloni.nuvox.net \
--to=wolf31o2@gentoo.org \
--cc=gentoo-dev@lists.gentoo.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox