From: Sune Kloppenborg Jeppesen <jaervosz@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] LinuxForum 2005 Copenhagen...
Date: Tue, 1 Mar 2005 00:03:36 +0100 [thread overview]
Message-ID: <200503010003.54726.jaervosz@gentoo.org> (raw)
In-Reply-To: <421B284E.80500@mayle.org>
[-- Attachment #1: Type: text/plain, Size: 630 bytes --]
Hi Douglas,
On Tuesday 22 February 2005 13:40, Douglas Mayle wrote:
> Hey all, I'm still just a lurker for the most part, but interested in
> becoming a dev. The reason why I'm bugging you all is I managed to
> convince my company to send me to LinuxConference next weekend in
> Copenhagen, and I was wondering who among you will be there. It'd be
> nice to meet some Gentoo devs, and possibly have somthing to do when I'm
> not being overwhelmed with a language I don't speak... :-)
> --
> gentoo-dev@gentoo.org mailing list
I'll be there Saturday.
--
Sune Kloppenborg Jeppesen
Gentoo Linux Security Team
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
prev parent reply other threads:[~2005-02-28 23:03 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-02-22 12:40 [gentoo-dev] LinuxForum 2005 Copenhagen Douglas Mayle
2005-02-23 13:41 ` Henrik Brix Andersen
2005-02-28 23:03 ` Sune Kloppenborg Jeppesen [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=200503010003.54726.jaervosz@gentoo.org \
--to=jaervosz@gentoo.org \
--cc=gentoo-dev@gentoo.org \
--cc=gentoo-dev@robin.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