* Smart HTTP Protocol
@ 2009-10-09 17:58 Michael Gaffney
2009-10-09 18:09 ` Shawn O. Pearce
0 siblings, 1 reply; 2+ messages in thread
From: Michael Gaffney @ 2009-10-09 17:58 UTC (permalink / raw)
To: git
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?
-Mike
^ permalink raw reply [flat|nested] 2+ messages in thread
* Re: Smart HTTP Protocol
2009-10-09 17:58 Smart HTTP Protocol Michael Gaffney
@ 2009-10-09 18:09 ` Shawn O. Pearce
0 siblings, 0 replies; 2+ messages in thread
From: Shawn O. Pearce @ 2009-10-09 18:09 UTC (permalink / raw)
To: Michael Gaffney; +Cc: git
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.
^ permalink raw reply [flat|nested] 2+ messages in thread
end of thread, other threads:[~2009-10-09 18:15 UTC | newest]
Thread overview: 2+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2009-10-09 17:58 Smart HTTP Protocol Michael Gaffney
2009-10-09 18:09 ` Shawn O. Pearce
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).