From: "Andreas K. Huettel" <dilfridge@gentoo.org>
To: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] vmware herd is empty
Date: Sun, 16 Jun 2013 17:25:10 +0200 [thread overview]
Message-ID: <201306161725.21440.dilfridge@gentoo.org> (raw)
In-Reply-To: <1371385238.10717.48.camel@localhost>
[-- Attachment #1: Type: Text/Plain, Size: 399 bytes --]
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.
--
Andreas K. Huettel
Gentoo Linux developer
dilfridge@gentoo.org
http://www.akhuettel.de/
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 966 bytes --]
next prev parent reply other threads:[~2013-06-16 15:23 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 [this message]
2013-06-21 13:59 ` Mike Gilbert
2013-06-21 15:47 ` Pacho Ramos
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=201306161725.21440.dilfridge@gentoo.org \
--to=dilfridge@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