From: Petr Baudis <pasky@ucw.cz>
To: Matt Mackall <mpm@selenic.com>
Cc: linux-kernel <linux-kernel@vger.kernel.org>,
git@vger.kernel.org, mercurial@selenic.com,
Linus Torvalds <torvalds@osdl.org>
Subject: Re: Mercurial 0.4e vs git network pull
Date: Thu, 12 May 2005 22:14:06 +0200 [thread overview]
Message-ID: <20050512201406.GJ324@pasky.ji.cz> (raw)
In-Reply-To: <20050512201116.GC5914@waste.org>
Dear diary, on Thu, May 12, 2005 at 10:11:16PM CEST, I got a letter
where Matt Mackall <mpm@selenic.com> told me that...
> On Thu, May 12, 2005 at 08:23:41PM +0200, Petr Baudis wrote:
> > Dear diary, on Thu, May 12, 2005 at 11:44:06AM CEST, I got a letter
> > where Matt Mackall <mpm@selenic.com> told me that...
> > > Mercurial is more than 10 times as bandwidth efficient and
> > > considerably more I/O efficient. On the server side, rsync uses about
> > > twice as much CPU time as the Mercurial server and has about 10 times
> > > the I/O and pagecache footprint as well.
> > >
> > > Mercurial is also much smarter than rsync at determining what
> > > outstanding changesets exist. Here's an empty pull as a demonstration:
> > >
> > > $ time hg merge hg://selenic.com/linux-hg/
> > > retrieving changegroup
> > >
> > > real 0m0.363s
> > > user 0m0.083s
> > > sys 0m0.007s
> > >
> > > That's a single http request and a one line response.
> >
> > So, what about comparing it with something comparable, say git pull over
> > HTTP? :-)
>
> ..because I get a headache every time I try to figure out how to use git? :-P
>
> Seriously, have a pointer to how this works?
Either you use cogito and just pass cg-clone an HTTP URL (to the git
repository as in the case of rsync -
http://www.kernel.org/pub/scm/cogito/cogito.git should work), or you
invoke git-http-pull directly (passing it desired commit ID of the
remote HEAD you want to fetch, and the URL; see
Documentation/git-http-pull.txt).
--
Petr "Pasky" Baudis
Stuff: http://pasky.or.cz/
C++: an octopus made by nailing extra legs onto a dog. -- Steve Taylor
next prev parent reply other threads:[~2005-05-12 20:07 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-05-12 9:44 Mercurial 0.4e vs git network pull Matt Mackall
2005-05-12 18:23 ` Petr Baudis
2005-05-12 20:11 ` Matt Mackall
2005-05-12 20:14 ` Petr Baudis [this message]
2005-05-12 20:57 ` Matt Mackall
2005-05-12 21:24 ` Daniel Barkalow
2005-05-12 22:29 ` Matt Mackall
2005-05-13 0:33 ` Daniel Barkalow
2005-05-13 1:11 ` Matt Mackall
2005-05-13 2:23 ` Daniel Barkalow
2005-05-13 2:44 ` Matt Mackall
2005-05-13 5:44 ` Petr Baudis
2005-05-15 8:54 ` Petr Baudis
2005-05-15 6:22 ` Ingo Molnar
-- strict thread matches above, loose matches on Subject: below --
2005-05-15 11:22 Adam J. Richter
2005-05-15 12:40 ` Petr Baudis
2005-05-16 22:22 ` Tristan Wibberley
2005-05-15 17:39 ` Matt Mackall
2005-05-15 18:23 ` Jeff Garzik
2005-05-16 1:12 ` Matt Mackall
2005-05-16 9:29 ` Matthias Urlichs
2005-05-15 11:52 Adam J. Richter
2005-05-15 14:23 ` Petr Baudis
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=20050512201406.GJ324@pasky.ji.cz \
--to=pasky@ucw.cz \
--cc=git@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mercurial@selenic.com \
--cc=mpm@selenic.com \
--cc=torvalds@osdl.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).