From: Ian Lance Taylor <iant@google.com>
To: Diego Novillo <dnovillo@google.com>
Cc: gcc@gcc.gnu.org, fortran@gcc.gnu.org, libstdc++@gcc.gnu.org,
java@gcc.gnu.org, binutils@sourceware.org, gdb@sourceware.org
Subject: Re: RFC - Initial planning for next Cauldron workshop
Date: Wed, 21 Nov 2012 19:42:00 -0000 [thread overview]
Message-ID: <CAKOQZ8xyLz1V9jP5KtOb2Wq1fM3NOdFLbyOWAO7gO23j=gnQgA@mail.gmail.com> (raw)
In-Reply-To: <20121121192716.GA17350@google.com>
On Wed, Nov 21, 2012 at 11:27 AM, Diego Novillo <dnovillo@google.com> wrote:
> Ian and I have started thinking about the next Cauldron. This
> time, we are thinking of organizing it in Mountain View, at
> Google's headquarters.
In case it's not obvious, this is Mountain View, California, USA.
> - Dates: We are looking at 12/Jul - 14/Jul, and 2/Aug - 4/Aug.
Note that these are over the weekend, which is when it is easier for
us to get space.
Ian
prev parent reply other threads:[~2012-11-21 19:42 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-21 19:27 Diego Novillo
2012-11-21 19:42 ` Ian Lance Taylor [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='CAKOQZ8xyLz1V9jP5KtOb2Wq1fM3NOdFLbyOWAO7gO23j=gnQgA@mail.gmail.com' \
--to=iant@google.com \
--cc=binutils@sourceware.org \
--cc=dnovillo@google.com \
--cc=fortran@gcc.gnu.org \
--cc=gcc@gcc.gnu.org \
--cc=gdb@sourceware.org \
--cc=java@gcc.gnu.org \
--cc=libstdc++@gcc.gnu.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).