From: Gaius Mulley <gaius@glam.ac.uk>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Jim Blandy <jimb@codesourcery.com>, gdb@sources.redhat.com
Subject: Re: annual question
Date: Mon, 25 Jun 2007 23:32:00 -0000 [thread overview]
Message-ID: <87fy4fsj9l.fsf@j228-gm.comp.glam.ac.uk> (raw)
In-Reply-To: <ufy4fojh4.fsf@gnu.org>
Eli Zaretskii <eliz@gnu.org> writes:
> > Cc: gdb@sources.redhat.com
> > From: Jim Blandy <jimb@codesourcery.com>
> > Date: Mon, 25 Jun 2007 11:50:23 -0700
> >
> >
> > Gaius Mulley <gaius@glam.ac.uk> writes:
> > > I was just wondering how many gdb people will be attending the GCC
> > > developers conference? I'm certainly looking forward to Daniel's talk
> > > - should be really interesting,
> >
> > I'll be there.
>
> Which reminds me the question I want to ask (annually) whenever this
> comes up: where is ``there''? how does one know when and where will
> such conferences take place, so one could plan in advance?
>
> Or do you-all assume that everyone who counts live within a shouting
> distance from the conference hall, and in any case in the -0700
> timezone?
Hi,
I believe there is still time (although it might be tight) to book
everything - from what I recall the cut off date is the 1st July (or
at least that is when printing, ordering etc occurs).
https://www.gccsummit.org/2007/login.php
once registered, you get a reminder in future years,
regards,
Gaius
next prev parent reply other threads:[~2007-06-25 23:32 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 18:14 Gaius Mulley
2007-06-25 18:38 ` Anmol P. Paralkar
2007-06-25 18:50 ` Jim Blandy
2007-06-25 20:41 ` Eli Zaretskii
2007-06-25 20:48 ` Daniel Jacobowitz
2007-06-26 17:58 ` Eric Weddington
2007-06-25 21:59 ` Jim Blandy
2007-06-25 23:32 ` Gaius Mulley [this message]
2007-06-25 20:28 ` Ulrich Weigand
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=87fy4fsj9l.fsf@j228-gm.comp.glam.ac.uk \
--to=gaius@glam.ac.uk \
--cc=eliz@gnu.org \
--cc=gdb@sources.redhat.com \
--cc=jimb@codesourcery.com \
/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