From: Jeff King <peff@peff.net>
To: Shawn Pearce <spearce@spearce.org>
Cc: Christian Couder <christian.couder@gmail.com>,
Theodore Ts'o <tytso@mit.edu>,
Luca Milanesio <luca.milanesio@gmail.com>,
git <git@vger.kernel.org>
Subject: Re: Next Git conference or meeting
Date: Wed, 3 Sep 2014 16:59:57 -0400 [thread overview]
Message-ID: <20140903205957.GA28644@peff.net> (raw)
In-Reply-To: <CAJo=hJs-wvT4fPA0Ad0tuOjBth0aRzbEFX6pu7N8Uq4TdToZgw@mail.gmail.com>
On Wed, Sep 03, 2014 at 10:15:15AM -0700, Shawn Pearce wrote:
> I hadn't realized Git is turning 10 next year. Just been too busy
> using Git to pay attention to its upcoming anniversary. Let me talk to
> some folks at Google and see if we can organize something here in
> Mountain View, or help the LinuxFoundation sponsor something.
Christian mentioned that he talked to some GitHub folks at LinuxCon.
Those folks have also started thinking about things. :)
Things are still very tentative at this point, but I think they are
considering something like the Git Merge conference we did earlier, and
doing it in June in Europe (maybe Paris). I know they were going to
reach out to Linux Foundation folks to try to jointly plan something,
but I don't know if that has happened yet.
So it seems there are a lot of different people who are all potentially
interested in planning or taking part, and they should all be talking to
each other. :)
-Peff
next prev parent reply other threads:[~2014-09-03 21:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-02 6:21 Next Git conference or meeting Christian Couder
2014-09-02 7:20 ` Luca Milanesio
2014-09-02 11:21 ` Theodore Ts'o
2014-09-02 13:15 ` Luca Milanesio
2014-09-02 13:51 ` Theodore Ts'o
2014-09-03 8:53 ` Christian Couder
2014-09-03 17:15 ` Shawn Pearce
2014-09-03 20:59 ` Jeff King [this message]
2014-09-04 7:40 ` Luca Milanesio
2014-09-09 15:49 ` Christian Couder
2014-09-10 20:14 ` Jeff King
2014-09-10 20:48 ` Christian Couder
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=20140903205957.GA28644@peff.net \
--to=peff@peff.net \
--cc=christian.couder@gmail.com \
--cc=git@vger.kernel.org \
--cc=luca.milanesio@gmail.com \
--cc=spearce@spearce.org \
--cc=tytso@mit.edu \
/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).