From: Pacho Ramos <pacho@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vmware herd is empty
Date: Fri, 21 Jun 2013 17:47:35 +0200 [thread overview]
Message-ID: <1371829655.2486.19.camel@localhost> (raw)
In-Reply-To: <CAJ0EP41jnBEau06pZ=5tt=a7ZB1xsGVSOEM1vjc6zWxnegOq2A@mail.gmail.com>
El vie, 21-06-2013 a las 09:59 -0400, Mike Gilbert escribió:
> On Sun, Jun 16, 2013 at 11:25 AM, Andreas K. Huettel
> <dilfridge@gentoo.org> wrote:
> > Am Sonntag, 16. Juni 2013, 14:20:38 schrieb Pacho Ramos:
> >> Will drop it in two weeks if nobody joins
> >>
> >> Thanks
> >
> > I've added myself to the vmware herd for now.
> >
> > However, I don't have much time and only really care about vmware-workstation,
> > so additional help is more than welcome.
> >
>
> I have a single Gentoo VM running on an ESX cluster if that helps.
>
> I'll take a crack at bug 471104
> (app-emulation/open-vm-tools-2013.04.16.1098359 version bump).
>
>
I guess dilfridge will welcome you in vmware herd then ;)
Thanks :)
next prev parent reply other threads:[~2013-06-21 15:47 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-06-16 12:20 [gentoo-dev] vmware herd is empty Pacho Ramos
2013-06-16 15:25 ` Andreas K. Huettel
2013-06-21 13:59 ` Mike Gilbert
2013-06-21 15:47 ` Pacho Ramos [this message]
2013-06-21 16:28 ` Andreas K. Huettel
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=1371829655.2486.19.camel@localhost \
--to=pacho@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