From: Andre Spiegel <spiegel@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: patch for documentation about version control
Date: Thu, 11 Nov 2004 21:59:27 +0100 [thread overview]
Message-ID: <1100206767.3428.224.camel@localhost> (raw)
In-Reply-To: <E1CSJdl-00033j-00@surf.glug.org>
On Thu, 2004-11-11 at 19:25 +0100, Thien-Thi Nguyen wrote:
> the vc-rcs-* funcs take 93% and 36% of the total time, respectively.
> unfortunately, nothing comes to mind for `vc-rcs-annotate-command'
> speedup.
So that means analyzing the tree takes longer than building it in the
first place, right? I'm not sure what algorithm you use for that, since
I don't understand your code ;-) Maybe there's a quadratic complexity
in there, which could be improved upon. Did you check how CVS does it?
We'd have to test on a few more real-world files, and on a real-world
machine (forgive me, I mean >300MHz :-) If it stays below a minute for
very large/complex change histories, I'd say we're still fine.
I have access to a few more complicated RCS masters, and will try your
code on those.
next prev parent reply other threads:[~2004-11-11 20:59 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-11-09 6:55 patch for documentation about version control Alex Ott
2004-11-09 9:13 ` Andre Spiegel
2004-11-12 9:11 ` Alex Ott
2004-11-09 18:21 ` Karl Fogel
2004-11-09 21:32 ` Stefan Monnier
2004-11-09 21:34 ` Stefan Monnier
2004-11-09 22:09 ` David Kastrup
2004-11-10 9:00 ` Thien-Thi Nguyen
2004-11-10 9:22 ` Andre Spiegel
2004-11-10 16:43 ` Thien-Thi Nguyen
2004-11-11 11:55 ` Andre Spiegel
2004-11-11 15:11 ` Stefan
2004-11-11 15:36 ` Andre Spiegel
2004-11-11 15:25 ` Thien-Thi Nguyen
2004-11-11 16:06 ` Thien-Thi Nguyen
2004-11-11 18:25 ` Thien-Thi Nguyen
2004-11-11 20:59 ` Andre Spiegel [this message]
2004-11-12 9:33 ` Thien-Thi Nguyen
2004-11-10 9:30 ` Andre Spiegel
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=1100206767.3428.224.camel@localhost \
--to=spiegel@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).