All of lore.kernel.org
 help / color / mirror / Atom feed
From: Michael J Gruber <git@drmicha.warpmail.net>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: Scott Chacon <schacon@gmail.com>,
	Christian Couder <christian.couder@gmail.com>,
	Michael Haggerty <mhagger@alum.mit.edu>,
	git list <git@vger.kernel.org>, Jeff King <peff@peff.net>,
	Junio C Hamano <gitster@pobox.com>,
	Shawn Pearce <spearce@spearce.org>,
	Heiko Voigt <hvoigt@hvoigt.net>,
	Jens Lehmann <Jens.Lehmann@web.de>,
	Thomas Rast <trast@student.ethz.ch>,
	Patrick Renaud <prenaud76@gmail.com>
Subject: Re: The GitTogether
Date: Sat, 22 Sep 2012 12:12:48 +0200	[thread overview]
Message-ID: <505D8F20.8060008@drmicha.warpmail.net> (raw)
In-Reply-To: <CAHGBnuPzb-jVqVAi+8=cSm=-mSQkVONbBaVyVf+s5L-KuBdUhg@mail.gmail.com>

Sebastian Schuberth venit, vidit, dixit 21.09.2012 16:33:
> On Fri, Sep 21, 2012 at 4:19 PM, Scott Chacon <schacon@gmail.com>
> wrote:
> 
>>>> I'm also very much interested in attending a gathering Berlin,
>>>> though preferably not in the first week of October. As I'm a
>>>> local, I could probably also help with finding a location if
>>>> necessary.
>> 
>> If you would like, I would love to get you in contact with the 
>> GitHubber in Berlin who is helping to secure a venue there so you
>> can help.
> 
> Sure, feel free to forward him / her my email address. I'm surprised 
> to hear that you had so much trouble finding / booking a location.
> For example, I would have expected one of the many co-working
> locations in Berlin [1] to be a good fit.
> 
> [1] http://www.coworking.de/regions/1-berlin

Also, there are many academic institutions, and at least some might be
happy to host an event like this (I'm thinking especially of the Zuse
institute). I had offered to help with hooking up with them  several
weeks ago already. So, it's really just a matter of communication.

Michael

  reply	other threads:[~2012-09-22 10:13 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-07-26 22:28 The GitTogether Scott Chacon
2012-07-27  6:12 ` Heiko Voigt
2012-07-27 11:45 ` Thomas Rast
2012-07-29 15:55   ` Jens Lehmann
2012-07-30 13:17     ` Michael J Gruber
2012-08-09 16:38       ` Michael J Gruber
2012-08-10 14:42         ` Patrick Renaud
2012-08-10 16:30           ` Junio C Hamano
2012-09-19 13:43 ` Michael Haggerty
2012-09-20 18:53   ` Sebastian Schuberth
2012-09-21  9:20     ` Christian Couder
2012-09-21 14:05       ` Shawn Pearce
2012-09-21 14:18         ` Jeff King
2012-09-21 15:23         ` Christian Couder
2012-09-21 16:43           ` Patrick Renaud
2012-09-21 16:45             ` Scott Chacon
2012-09-21 16:55               ` Patrick Renaud
2012-09-21 16:57                 ` Luca Milanesio
2012-09-21 14:19       ` Scott Chacon
2012-09-21 14:33         ` Sebastian Schuberth
2012-09-22 10:12           ` Michael J Gruber [this message]
2012-09-22 10:45             ` Sebastian Schuberth
2012-09-22 18:09             ` 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=505D8F20.8060008@drmicha.warpmail.net \
    --to=git@drmicha.warpmail.net \
    --cc=Jens.Lehmann@web.de \
    --cc=christian.couder@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hvoigt@hvoigt.net \
    --cc=mhagger@alum.mit.edu \
    --cc=peff@peff.net \
    --cc=prenaud76@gmail.com \
    --cc=schacon@gmail.com \
    --cc=spearce@spearce.org \
    --cc=sschuberth@gmail.com \
    --cc=trast@student.ethz.ch \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.