git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Michael Haggerty <mhagger@alum.mit.edu>
To: Scott Chacon <schacon@gmail.com>
Cc: 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>,
	Michael J Gruber <git@drmicha.warpmail.net>,
	Jens Lehmann <Jens.Lehmann@web.de>,
	Thomas Rast <trast@student.ethz.ch>,
	Patrick Renaud <prenaud76@gmail.com>
Subject: Re: The GitTogether
Date: Wed, 19 Sep 2012 15:43:29 +0200	[thread overview]
Message-ID: <5059CC01.2080205@alum.mit.edu> (raw)
In-Reply-To: <CAP2yMaJzJyw=9DqJzUXkkQjz_jcqB4pH=FfHFRiftC9=yC7dvg@mail.gmail.com>

On 07/27/2012 12:28 AM, Scott Chacon wrote:
> [...]
> I would like to see two different gatherings this year - one that
> would be user-centric to gather people that use Git together with some
> of the developers and talk about Git from a user's perspective.  The
> other event I would like to see would be a gathering of many of the
> core Git developers in a sort of hacker summit.
> 
> GitHub would like to volunteer to organize and pay for these events
> this year.  I would like to hold the developer-centric one in Berlin
> in early October (a few weeks before the Mentor Summit this time) and
> the user one in January or February of next year.
> [...]

Is there any news about the proposed gatherings?  I would be quite
interested in attending the developer meeting.  October is just around
the corner...what's up?

Michael

-- 
Michael Haggerty
mhagger@alum.mit.edu
http://softwareswirl.blogspot.com/

  parent reply	other threads:[~2012-09-19 13:43 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 [this message]
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
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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=5059CC01.2080205@alum.mit.edu \
    --to=mhagger@alum.mit.edu \
    --cc=Jens.Lehmann@web.de \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=hvoigt@hvoigt.net \
    --cc=peff@peff.net \
    --cc=prenaud76@gmail.com \
    --cc=schacon@gmail.com \
    --cc=spearce@spearce.org \
    --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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

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).