From: Christian Couder <chriscool@tuxfamily.org>
To: "Shawn O. Pearce" <spearce@spearce.org>
Cc: git@vger.kernel.org
Subject: GitTogether '09
Date: Wed, 18 Mar 2009 06:51:33 +0100 [thread overview]
Message-ID: <200903180651.33381.chriscool@tuxfamily.org> (raw)
In-Reply-To: <20090310001613.GL11989@spearce.org>
Le mardi 10 mars 2009, Shawn O. Pearce a écrit :
> Folks, its that time of year again. We need to apply to be a
> mentoring organization for Google Summer of Code 2009.
Maybe we could also start discussing GitTogether '09 location and date.
I have added a GitTogether '09 heading to the wiki page and a few location
and date ideas:
http://git.or.cz/gitwiki/GitTogether
The location and dates are:
* San Francisco in October, just after the Google Summer of Code Mentor
* Portland Oregon in September, during or after LinuxCon
(http://events.linuxfoundation.org/events/linuxcon) and/or Linux Plumbers
Conference (http://linuxplumbersconf.org/)
Best regards,
Christian.
next prev parent reply other threads:[~2009-03-18 5:54 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-03-10 0:16 Google Summer of Code 2009 - Organization Application Shawn O. Pearce
2009-03-10 12:42 ` Jakub Narebski
2009-03-10 14:24 ` Shawn O. Pearce
2009-03-18 5:51 ` Christian Couder [this message]
2009-03-18 6:46 ` GitTogether '09 Sverre Rabbelier
2009-03-18 7:05 ` Christian Couder
2009-03-18 9:54 ` Sverre Rabbelier
2009-03-18 14:35 ` Shawn O. Pearce
2009-03-18 14:53 ` Johannes Schindelin
2009-03-18 15:55 ` Shawn O. Pearce
2009-03-22 22:00 ` [Gittogether] " Sam Vilain
2009-03-22 22:01 ` Sam Vilain
2009-03-18 16:05 ` Scott Chacon
2009-03-18 16:11 ` Shawn O. Pearce
-- strict thread matches above, loose matches on Subject: below --
2009-08-28 18:53 gittogether '09 Brandon Casey
2009-08-28 19:17 ` Shawn O. 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=200903180651.33381.chriscool@tuxfamily.org \
--to=chriscool@tuxfamily.org \
--cc=git@vger.kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).