From: Sverre Rabbelier <srabbelier@gmail.com>
To: Christian Couder <chriscool@tuxfamily.org>,
"Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org, gittogether@lists.utsl.gen.nz
Subject: Re: GitTogether '09
Date: Wed, 18 Mar 2009 10:54:49 +0100 [thread overview]
Message-ID: <fabb9a1e0903180254u5569e9f5u5e1aa43fa2d1d178@mail.gmail.com> (raw)
In-Reply-To: <200903180805.32440.chriscool@tuxfamily.org>
Heya,
On Wed, Mar 18, 2009 at 08:05, Christian Couder <chriscool@tuxfamily.org> wrote:
> I thought that it was only one international airplane ticket last year,
> except perhaps when there are no US based mentor. And we are not sure that
> Google or another company in the Bay Area will be able to host us this
> year. So the cost of hosting the GitTogether might be higher than the cost
> of a few airplane tickets.
Last year Google provided two international airplane tickets and was
able to host us, we can at least ask them to host us again this year
(if that is what we decide on).
Shawn, how likely is it that Google will provide hosting for another
GitTogether this year?
--
Cheers,
Sverre Rabbelier
next prev parent reply other threads:[~2009-03-18 9:56 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:16 Google Summer of Code 2009 - Organization Application Shawn O. Pearce
2009-03-10 12:42 ` Jakub Narebski
2009-03-10 14:24 ` Shawn O. Pearce
2009-03-18 5:51 ` GitTogether '09 Christian Couder
2009-03-18 6:46 ` Sverre Rabbelier
2009-03-18 7:05 ` Christian Couder
2009-03-18 9:54 ` Sverre Rabbelier [this message]
2009-03-18 14:35 ` Shawn O. Pearce
2009-03-18 14:53 ` Johannes Schindelin
2009-03-18 15:55 ` Shawn O. Pearce
2009-03-22 22:00 ` [Gittogether] " Sam Vilain
2009-03-22 22:01 ` Sam Vilain
2009-03-18 16:05 ` Scott Chacon
2009-03-18 16:11 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2009-08-28 18:53 gittogether '09 Brandon Casey
2009-08-28 19:17 ` Shawn O. Pearce
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=fabb9a1e0903180254u5569e9f5u5e1aa43fa2d1d178@mail.gmail.com \
--to=srabbelier@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--cc=gittogether@lists.utsl.gen.nz \
--cc=spearce@spearce.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 NNTP newsgroup(s).