From: Junio C Hamano <gitster@pobox.com>
To: Jeff King <peff@peff.net>
Cc: Shawn Pearce <spearce@spearce.org>,
Scott Chacon <schacon@gmail.com>, git <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] GitTogether 2011 - Oct 24th/25th
Date: Wed, 07 Sep 2011 14:00:24 -0700 [thread overview]
Message-ID: <7v7h5k2hlj.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <20110907193006.GB13364@sigill.intra.peff.net> (Jeff King's message of "Wed, 7 Sep 2011 15:30:06 -0400")
Jeff King <peff@peff.net> writes:
> I think that's reasonable, especially as we grow. However, one of the
> valuable things (for me, anyway) in previous GitTogethers is throwing
> all of these people together to some degree. I'm not terribly interested
> in day-to-day Gerrit issues, but sometimes the discussions start from
> some minor Gerrit annoyance, and we end up realizing that the right
> solution involves changes at a more fundamental layer, and all of git is
> better as a result. I'd hate to lose that developer/user interaction.
Same here, as I have been meaning to gauge interests from non-Gerrit
people on issues identified in Gerrit land (e.g. expand-refs).
> Maybe we can be segmented for part of the conference, and then bring
> everybody together for other parts. I dunno. I guess that involves
> predicting which parts will be useful for everybody to be together.
Also we would need to predict what parts we will have to begin with ;-).
next prev parent reply other threads:[~2011-09-07 21:00 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-05 19:56 [ANNOUNCE] GitTogether 2011 - Oct 24th/25th Shawn Pearce
2011-09-07 17:11 ` Scott Chacon
2011-09-07 18:38 ` Shawn Pearce
2011-09-07 19:30 ` Jeff King
2011-09-07 20:44 ` Scott Chacon
2011-09-07 21:06 ` Shawn Pearce
2011-09-07 21:00 ` Junio C Hamano [this message]
2011-09-09 23:10 ` Shawn 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=7v7h5k2hlj.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--cc=schacon@gmail.com \
--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