From: "Eric S. Raymond" <esr@thyrsus.com>
To: David Kastrup <dak@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Emacs-devel Digest, Vol 47, Issue 14
Date: Wed, 2 Jan 2008 11:06:41 -0500 [thread overview]
Message-ID: <20080102160641.GA19672@thyrsus.com> (raw)
In-Reply-To: <86lk78jk3j.fsf@lola.quinscape.zz>
David Kastrup <dak@gnu.org>:
> "Eric S. Raymond" <esr@thyrsus.com> writes:
>
> > I second this recommendation. I am not yet sure Mercurial is the
> > overall best-of-breed, but it is the most accessible of the big three
> > (git, bzr, hg) and seems to have the best UI design.
>
> Before making a decision, one should try the candidates on the Emacs
> repository data which will constitute our real workload.
Agreed. In fact, you may have solved a problem for me by pointing
this out -- I've been casting around for a large real-world codebase to
do comparative benchmarks against, and Emacs might do nicely.
> The Emacs history is very unusual in size and structure.
It's larger than most, certainly. What do you mean by unusual
in "structure"?
> Actually, this needs to be checked under different operating systems
> (and their file systems) too. At least with git, the profiling and
> tuning of the operations happens mostly on GNU/Linux and this shows.
Yes, performance on other systems is reputed to be poor.
--
<a href="http://www.catb.org/~esr/">Eric S. Raymond</a>
next prev parent reply other threads:[~2008-01-02 16:06 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20080102144739.057262C83E2@grelber.thyrsus.com>
2008-01-02 15:43 ` Emacs-devel Digest, Vol 47, Issue 14 Eric S. Raymond
2008-01-02 15:57 ` David Kastrup
2008-01-02 16:06 ` Eric S. Raymond [this message]
2008-01-02 16:14 ` David Kastrup
2008-01-02 16:54 ` Eric S. Raymond
2008-01-21 11:54 ` Sascha Wilde
2008-01-21 19:43 ` Martin Geisler
2008-01-22 10:43 ` Sascha Wilde
2008-01-22 18:46 ` Mercurial CVS mirror (was: Emacs-devel Digest, Vol 47, Issue 14) Martin Geisler
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: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080102160641.GA19672@thyrsus.com \
--to=esr@thyrsus.com \
--cc=dak@gnu.org \
--cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).