From: "Shawn O. Pearce" <spearce@spearce.org>
To: Michael Gaffney <mr.gaffo@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Smart HTTP Protocol
Date: Fri, 9 Oct 2009 11:09:18 -0700 [thread overview]
Message-ID: <20091009180918.GY9261@spearce.org> (raw)
In-Reply-To: <4ACF79E0.5000606@gmail.com>
Michael Gaffney <mr.gaffo@gmail.com> wrote:
> What ended up being the status on this? From the last I saw, the
> protocol and the fallover smart to dumb had all been worked out. It was
> just that people were waiting on an implementation server side of the
> protocol before the client was implemented?
Uh, did you read my thread from last night at 10:30 pm called
"Return of smart HTTP" ?
Previous to this week we did not have a working server, OR a working
client, OR even a final spec.
I've started working on smart HTTP full time, and am not touching
any other project until the patches are being carried in Junio's
"next". I'm not going to rush the reviews on the list, but so long
as there is code for me to write/fix or documentation to write/fix
I'm refusing to touch another task.
I have it full implemented in JGit (client and server). I have
most of the server implemented in C Git. I'm working on the C Git
client today.
--
Shawn.
prev parent reply other threads:[~2009-10-09 18:15 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-09 17:58 Smart HTTP Protocol Michael Gaffney
2009-10-09 18:09 ` Shawn O. Pearce [this message]
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=20091009180918.GY9261@spearce.org \
--to=spearce@spearce.org \
--cc=git@vger.kernel.org \
--cc=mr.gaffo@gmail.com \
/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).