From: "Shawn O. Pearce" <spearce@spearce.org>
To: git <git@vger.kernel.org>
Subject: [ANNOUNCE] GitTogether '10 (Developer/User Summit Oct 25-27)
Date: Wed, 30 Jun 2010 14:17:13 -0700 [thread overview]
Message-ID: <20100630211713.GI2337@spearce.org> (raw)
Google is hosting GitTogether '10, October 25th through 27th,
at its Mountain View, CA headquarters.
Like last year (and the year before that!), this GitTogether
immediately follows the Google Summer of Code mentor summit, so
some of our end-user groups may already have representatives in
the area and might like to attend. We've timed the GitTogether
to follow the summit so we can get some users to attend while they
are still in the area.
Git contributors and users alike are welcome to attend. Admission is
free, but you will need to arrange for your own travel and lodging.
If you are looking at flights try the SJC and SFO airports.
SFO usually has cheaper flights as its a bigger, more active airport.
We are looking to solicit proposals for talks, round-table
discussions, centers of focus for patch hack-a-thons, etc.
A Git Wiki page is being used for planning:
https://git.wiki.kernel.org/index.php/GitTogether10
If you would like to attend, please add your name to the Attendees
list on the wiki page.
--
Shawn.
reply other threads:[~2010-06-30 21:17 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20100630211713.GI2337@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).