From: Luke Diamand <luke@diamand.org>
To: Jeff King <peff@peff.net>
Cc: luca.milanesio@gmail.com, Git Users <git@vger.kernel.org>
Subject: Re: [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels
Date: Wed, 14 Nov 2018 12:31:22 +0000 [thread overview]
Message-ID: <CAE5ih791JybFYb4=Zw6P+fJ7rpWtsaCeUVJMcN=d91AO0sFcVQ@mail.gmail.com> (raw)
In-Reply-To: <20181109104820.GA9900@sigill.intra.peff.net>
On Fri, 9 Nov 2018 at 10:48, Jeff King <peff@peff.net> wrote:
>
> On Fri, Nov 09, 2018 at 10:44:10AM +0000, Luca Milanesio wrote:
>
> > > On 9 Nov 2018, at 10:42, Jeff King <peff@peff.net> wrote:
> > >
> > > Git Merge 2019 is happening on February 1st. There will be a
> > > Contributor's Summit the day before. Here are the details:
> > >
> > > When: Thursday, January 31, 2019. 10am-5pm.
> > > Where: The Egg[1], Brussels, Belgium
> > > What: Round-table discussion about Git
> > > Who: All contributors to Git or related projects in the Git ecosystem
> > > are invited; if you're not sure if you qualify, please ask!
> >
> > Hi Jeff,
> > is Gerrit included in the "Git ecosystem"?
>
> Yeah, I think so. At least the Git parts of it. :)
git-p4?
(The git parts obviously!)
>
> -Peff
next prev parent reply other threads:[~2018-11-14 12:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-09 10:42 [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels Jeff King
2018-11-09 10:44 ` Luca Milanesio
2018-11-09 10:48 ` Jeff King
2018-11-14 12:31 ` Luke Diamand [this message]
2018-11-14 12:53 ` Jeff King
2019-02-20 12:48 ` Git Merge Conference Recordings [was: Re: [ANNOUNCE] Git Merge Contributor's Summit Jan 31, 2019, Brussels] Thomas Braun
2019-02-20 13:03 ` Ævar Arnfjörð Bjarmason
2019-02-21 4:59 ` Jeff King
2019-02-21 8:22 ` Jeff King
2019-02-21 21:27 ` Thomas Braun
2019-03-16 15:31 ` 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
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='CAE5ih791JybFYb4=Zw6P+fJ7rpWtsaCeUVJMcN=d91AO0sFcVQ@mail.gmail.com' \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=luca.milanesio@gmail.com \
--cc=peff@peff.net \
/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).