From: Junio C Hamano <gitster@pobox.com>
To: Git Mailing List <git@vger.kernel.org>
Cc: "Jeff King" <peff@peff.net>,
spearce@spearce.org, "Ævar Arnfjörð" <avarab@gmail.com>
Subject: Re: Is anyone working on a next-gen Git protocol?
Date: Sun, 21 Oct 2012 21:59:36 -0700 [thread overview]
Message-ID: <CAPc5daUJ9zZXci=N+v819FsMKvEaY7ar6xwG9TRt0CP=HBzbZQ@mail.gmail.com> (raw)
In-Reply-To: <7va9vxq5gp.fsf@alter.siamese.dyndns.org>
On Sun, Oct 7, 2012 at 3:31 PM, Junio C Hamano <gitster@pobox.com> wrote:
>
> I and Shawn helped privately somebody from Gerrit circle, where the
> initial ref advertisement is a huge problem (primarily because they
> add tons of refs to one commit that eventually goes to their
> integration branch), to coming up with a problem description and
> proposal document to kick-start a discussion some time ago, but not
> much has happened since. Unless I hear from them soonish, I'll send
> a cleaned-up version of the draft before I leave for my vacation.
Which I forgot and never happened. Here is a link (not cleaned-up)
http://tinyurl.com/WhoSpeaksFirstInGit
next prev parent reply other threads:[~2012-10-22 5:00 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-10-07 19:57 Is anyone working on a next-gen Git protocol? Ævar Arnfjörð Bjarmason
2012-10-07 20:22 ` Ilari Liusvaara
2012-10-07 22:08 ` Jeff King
2012-10-07 22:31 ` Junio C Hamano
2012-10-22 4:59 ` Junio C Hamano [this message]
2012-10-08 9:05 ` Andreas Ericsson
2012-10-08 16:27 ` Junio C Hamano
2012-10-10 19:13 ` Steffen Prohaska
2012-10-10 20:46 ` Junio C Hamano
2012-10-10 22:32 ` Philip Oakley
2012-10-11 1:44 ` Nguyen Thai Ngoc Duy
2012-10-11 3:08 ` 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
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='CAPc5daUJ9zZXci=N+v819FsMKvEaY7ar6xwG9TRt0CP=HBzbZQ@mail.gmail.com' \
--to=gitster@pobox.com \
--cc=avarab@gmail.com \
--cc=git@vger.kernel.org \
--cc=peff@peff.net \
--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.
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).