From: Eli Zaretskii <eliz@gnu.org>
To: Stephen Berman <stephen.berman@gmx.net>
Cc: emacs-devel@gnu.org
Subject: Re: vc-print-log vs. bzr log
Date: Sat, 15 Sep 2012 16:51:33 +0300 [thread overview]
Message-ID: <83zk4rs8be.fsf@gnu.org> (raw)
In-Reply-To: <87ipbfcu4o.fsf@rosalinde.fritz.box>
> From: Stephen Berman <stephen.berman@gmx.net>
> Date: Sat, 15 Sep 2012 15:07:03 +0200
>
> When I'm visiting a file on a local branch of the Emacs bzr trunk and
> type `M-! bzr log -r-1 RET' I see the log entry in less than one second.
> When I type `C-x v l RET RET' ±19 seconds elapse before the log is
> displayed (and the lag time is the same if I limit the display to one
> entry). Is this time difference expected?
Yes, to some degree, because these two commands do 2 different things.
The first one shows the last commit in the branch. The second one
shows the commits only to the file you are visiting, which means
digging deeper into the version history.
However, even if the file you are visiting is the one modified by the
last revision, bzr is slower when a file argument is passed. I guess
this is something to report as a bug to bzr bug tracker.
Btw, did you really mean "C-x v l RET RET", or did you mean something
like "C-u C-x v l RET 1 RET"? If the former, then by default C-x v l
does not prompt for anything, so I have no opportunity to type RET
twice.
prev parent reply other threads:[~2012-09-15 13:51 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-15 13:07 vc-print-log vs. bzr log Stephen Berman
2012-09-15 13:37 ` Andreas Schwab
2012-09-15 14:56 ` Stephen Berman
2012-09-15 15:45 ` Eli Zaretskii
2012-09-15 16:04 ` Stephen Berman
2012-09-15 16:28 ` Eli Zaretskii
2012-09-15 17:36 ` Stephen Berman
2012-09-15 17:56 ` Andreas Schwab
2012-09-15 19:36 ` Eli Zaretskii
2012-09-15 13:51 ` Eli Zaretskii [this message]
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=83zk4rs8be.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=stephen.berman@gmx.net \
/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).