From: Dennis Luehring <dl.soluz@gmx.net>
To: unlisted-recipients:; (no To-header on input)
Cc: Git <git@vger.kernel.org>
Subject: Re: question about: Facebook makes Mercurial faster than Git
Date: Mon, 10 Mar 2014 12:42:17 +0100 [thread overview]
Message-ID: <531DA519.8090509@gmx.net> (raw)
In-Reply-To: <CANgJU+W+f3KUxehDGxd+f77RO24VadsnOV=szE2MkBXjs8wDCQ@mail.gmail.com>
Am 10.03.2014 12:28, schrieb demerphq:
> I had the impression, and I would not be surprised if they had the
> impression that the git development community is relatively
> unconcerned about performance issues on larger repositories.
so the question is if the git community is interested in beeing
competive in such
large scale scenarios - something what mercurial seems to be now out of
the box
next prev parent reply other threads:[~2014-03-10 11:42 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-03-10 10:07 question about: Facebook makes Mercurial faster than Git Dennis Luehring
2014-03-10 10:13 ` David Lang
2014-03-10 17:51 ` Ondřej Bílka
2014-03-10 17:56 ` David Lang
2014-03-10 20:22 ` Martin Langhoff
2014-03-11 14:23 ` Ondřej Bílka
2014-03-10 11:28 ` demerphq
2014-03-10 11:42 ` Dennis Luehring [this message]
2014-03-10 12:10 ` Johan Herland
2014-03-10 14:48 ` Michael Haggerty
2014-03-10 14:18 ` Karsten Blees
2014-03-14 12:58 ` Duy Nguyen
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=531DA519.8090509@gmx.net \
--to=dl.soluz@gmx.net \
--cc=git@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.