From: Thomas Rast <trast@student.ethz.ch>
To: Scott Chacon <schacon@gmail.com>
Cc: git list <git@vger.kernel.org>
Subject: Re: Git Merge 2013 Conference, Berlin
Date: Mon, 18 Feb 2013 21:52:34 +0100 [thread overview]
Message-ID: <87mwv1uyy5.fsf@pctrast.inf.ethz.ch> (raw)
In-Reply-To: <CAP2yMaJyCi5tvFZ5hVpVULR=oKgfc-b0zb8baxFDhNqmu+W_Bg@mail.gmail.com> (Scott Chacon's message of "Wed, 23 Jan 2013 11:27:16 -0800")
Scott Chacon <schacon@gmail.com> writes:
> We're starting off in Berlin, May 9-11th. GitHub has secured
> conference space at the Radisson Blu Berlin for those days. I have a
> smaller room for the first day so we can get 30-40 Git implementors
> together to talk about the future of Git and whatnot.
[...]
> http://git-merge.com/
So this has been fairly quiet -- is anyone else coming? :-)
You should probably talk to Radisson Blu about their cancellation
conditions, so as to avoid some nasty arguments. Their "Features" say
Cancellations free of charge can be made until 4 weeks prior to
arrival date.
while their "Hotel Policy" says
Cancellation Policy:
- Cancel by 6:00 PM hotel time on May 09 2013 = no penalty.
which is clearly contradictory.
--
Thomas Rast
trast@{inf,student}.ethz.ch
next prev parent reply other threads:[~2013-02-18 20:53 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-23 19:27 Git Merge 2013 Conference, Berlin Scott Chacon
2013-02-18 20:52 ` Thomas Rast [this message]
2013-02-18 21:17 ` Jeff King
2013-02-18 21:29 ` Scott Chacon
2013-02-19 15:20 ` Michael J Gruber
2013-02-19 15:41 ` Michael J Gruber
2013-02-19 15:46 ` Scott Chacon
2013-02-19 19:19 ` Junio C Hamano
2013-02-19 19:23 ` Scott Chacon
2013-02-19 21:26 ` Junio C Hamano
2013-02-19 22:47 ` Scott Chacon
2013-02-19 23:47 ` Junio C Hamano
2013-02-20 8:05 ` Michael J Gruber
2013-02-20 8:57 ` Jeff King
2013-05-10 19:10 ` Sebastian Schuberth
2013-05-10 19:16 ` Scott Chacon
2013-05-29 8:44 ` Enrico Weigelt
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=87mwv1uyy5.fsf@pctrast.inf.ethz.ch \
--to=trast@student.ethz.ch \
--cc=git@vger.kernel.org \
--cc=schacon@gmail.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;
as well as URLs for NNTP newsgroup(s).