From: Jakub Narebski <jnareb@gmail.com>
To: "Matthias Andree" <matthias.andree@gmx.de>
Cc: "Christian Couder" <chriscool@tuxfamily.org>,
git@vger.kernel.org, "James Cloos" <cloos@jhcloos.com>
Subject: Re: Google Code: Support for Mercurial and Analysis of Git and Mercurial
Date: Sun, 26 Apr 2009 21:57:36 +0200 [thread overview]
Message-ID: <200904262157.39450.jnareb@gmail.com> (raw)
In-Reply-To: <200904261209.08108.jnareb@gmail.com>
On Sun, 26 April 2009, Jakub Narebski wrote:
> On Sun, 26 April 2009, Matthias Andree wrote:
> > Am 26.04.2009, 10:16 Uhr, schrieb Jakub Narebski <jnareb@gmail.com>:
> [...]
> > > The deciding feature (well, one of deciding features) was the fact
> > > that Mercurial has better HTTP support... I guess (it was not obvious
> > > from the analysis, but it was hinted at) that Mercurial uses its
> > > custom protocol over HTTP, as opposed to "dumb" HTTP protocol support
> > > in Git.
> > >
> > > Perhaps it is time to restart work on _"smart" HTTP protocol_?
> >
> > That would certainly be useful, but the "packs" approach is something that
> > may make this more difficult than for Mercurial. Git+SSH works rather well
> > though.
>
> As you can find in mailing list archives the design part of "tunelling"
> pack protocol over HTTP, using git-aware server (for example some CGI
> script, or simple HTTP server like Mercurial's hg-serve), is done.
[...]
See thread named "More on git over HTTP POST" and its predecessor
http://permalink.gmane.org/gmane.comp.version-control.git/91196
http://thread.gmane.org/gmane.comp.version-control.git/91104/focus=91196
--
Jakub Narebski
Poland
next prev parent reply other threads:[~2009-04-26 19:59 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-26 5:03 Google Code: Support for Mercurial and Analysis of Git and Mercurial Christian Couder
2009-04-26 7:12 ` Michael Witten
2009-04-26 8:16 ` Jakub Narebski
2009-04-26 8:23 ` Paolo Ciarrocchi
2009-04-26 10:07 ` Johannes Schindelin
2009-04-26 10:16 ` Jakub Narebski
2009-04-26 10:18 ` Johannes Schindelin
2009-04-26 12:02 ` Alex Blewitt
2009-04-27 20:31 ` Shawn O. Pearce
2009-04-26 10:21 ` Paolo Ciarrocchi
2009-04-26 9:21 ` Matthias Andree
2009-04-26 10:09 ` Jakub Narebski
2009-04-26 11:47 ` Matthias Andree
2009-04-26 19:57 ` Jakub Narebski [this message]
2009-04-26 14:54 ` A Large Angry SCM
2009-04-26 16:45 ` Michael Witten
2009-04-26 16:56 ` Johannes Schindelin
2009-04-26 17:33 ` A Large Angry SCM
2009-04-26 17:45 ` Johannes Schindelin
2009-04-26 18:00 ` A Large Angry SCM
2009-04-26 18:59 ` James Cloos
2009-04-26 10:13 ` Johannes Schindelin
2009-04-26 16:47 ` Michael Witten
2009-04-26 22:24 ` Miles Bader
2009-04-27 21:15 ` Shawn O. Pearce
2009-04-30 0:00 ` Mark Lodato
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=200904262157.39450.jnareb@gmail.com \
--to=jnareb@gmail.com \
--cc=chriscool@tuxfamily.org \
--cc=cloos@jhcloos.com \
--cc=git@vger.kernel.org \
--cc=matthias.andree@gmx.de \
/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).