From: Michael Imhof <tantive@gentoo.org>
To: gentoo-dev@robin.gentoo.org
Cc: gentoo-dev@robin.gentoo.org
Subject: Re: [gentoo-dev] GUADEC 2005?
Date: Tue, 15 Mar 2005 03:26:09 +0100 [thread overview]
Message-ID: <423647C1.4040501@gentoo.org> (raw)
In-Reply-To: <42335975.10601@gentoo.org>
[-- Attachment #1: Type: text/plain, Size: 401 bytes --]
Hi,
Daniel Drake wrote:
> Hi,
>
> Is anyone planning to head out to GUADEC this year? (May 29th-31st,
> Stuttgart, Germany)
> Have Gentoo participated here before?
Nope, i participated in the KDE Konference last year (in Stuttgart as well).
>
> I'm planning to go, assuming that I do not have any exams those days.
heh, i will try to attend it as well as i'm living in stuttgart ;)
Regards
Tantive
[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 252 bytes --]
next prev parent reply other threads:[~2005-03-15 2:26 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-03-12 21:04 [gentoo-dev] GUADEC 2005? Daniel Drake
2005-03-13 9:43 ` Markus Nigbur
2005-03-14 9:51 ` Zaheer Merali
2005-03-15 2:26 ` Michael Imhof [this message]
2005-03-20 10:06 ` Sebastian Bergmann
2005-03-21 23:36 ` Andrew Cowie
2005-03-22 0:09 ` Lars Weiler
2005-03-24 14:14 ` Karl Trygve Kalleberg
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=423647C1.4040501@gentoo.org \
--to=tantive@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