git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Junio C Hamano <gitster@pobox.com>
To: Patrick Renaud <prenaud76@gmail.com>
Cc: Michael J Gruber <git@drmicha.warpmail.net>,
	Jens Lehmann <Jens.Lehmann@web.de>,
	Thomas Rast <trast@student.ethz.ch>,
	Scott Chacon <schacon@gmail.com>, git list <git@vger.kernel.org>,
	Jeff King <peff@peff.net>, Shawn Pearce <spearce@spearce.org>
Subject: Re: The GitTogether
Date: Fri, 10 Aug 2012 09:30:53 -0700	[thread overview]
Message-ID: <7vwr16k8ua.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <CAC+LNEQB-B5L2CV2pONsOyD-VE4SW36c9SKxdOcYGBQbA-d4hQ@mail.gmail.com> (Patrick Renaud's message of "Fri, 10 Aug 2012 10:42:50 -0400")

Patrick Renaud <prenaud76@gmail.com> writes:

> I am not sure to understand why having two physically disconnected
> events, in time and in place. Personally I'd rather see one event,
> maybe longer than the previous occurrences to accommodate for the user
> and developer centric topics.

I think a separate event at a venue on different continent was
proposed primarily to avoid "annual GitTogether always at Mountain
View" that has been unfriendly to our European friends (mitigated
somewhat by having it immediately after GSoC mentor summit).  I
agree it may be a better solution to that issue to move the two
things to the same venue that moves from year to year.

The kernel folks have the (by invitation only) Kernel Summit
immediately before the wider end user conference at the same place,
which used to be always Ottawa but the venue moves around from year
to year these days.  That is something we could learn from them.

  reply	other threads:[~2012-08-10 16:31 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 [this message]
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
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=7vwr16k8ua.fsf@alter.siamese.dyndns.org \
    --to=gitster@pobox.com \
    --cc=Jens.Lehmann@web.de \
    --cc=git@drmicha.warpmail.net \
    --cc=git@vger.kernel.org \
    --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).