From: Dmitry Gutov <dgutov@yandex.ru>
To: Lars Ingebrigtsen <larsi@gnus.org>, Lars Ljung <lars@matholka.se>
Cc: Glenn Morris <rgm@gnu.org>,
Stefan Monnier <monnier@iro.umontreal.ca>,
13547@debbugs.gnu.org
Subject: bug#13547: svn annotate - incorrect previous/next revision
Date: Sat, 31 Jul 2021 05:40:37 +0300 [thread overview]
Message-ID: <265e7b3c-06c5-7fa4-81e4-0a75fea41765@yandex.ru> (raw)
In-Reply-To: <87v94snhir.fsf@gnus.org>
Hi!
On 30.07.2021 14:54, Lars Ingebrigtsen wrote:
> Lars Ingebrigtsen<larsi@gnus.org> writes:
>
>>>> Thanks. I guess the drawback here is, that will contact the svn
>>>> repository, which may be on a remote server, so could be slow.
>>>>
>>>> It seems this is used by vc-annotate, vc-rollback, and vc-diff.
>>> Yes, it will be slower. But as far as I know there is no other way to
>>> get the previous/next revision of a file.
>> I haven't used svn in many years, so I don't have much of an opinion
>> here. I've respun the patch for Emacs 28; included below.
>>
>> Anybody got an opinion here?
> I forgot to put Dmitry in the CCs; perhaps he'll have an opinion.
Since this is about SVN, it's hard for me to have an opinion as well:
all practical recollections are from ~10 years ago. How slow are SVN
servers to respond to requests like this these days?
Could someone also describe the effect that our current "not correct"
revision numbers have? Do they trigger errors? Do them cause
'vc-annotate' to show wrong file contents?
If it's either of these, then we probably should go ahead with the patch.
next prev parent reply other threads:[~2021-07-31 2:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-01-25 9:29 bug#13547: svn annotate - incorrect previous/next revision Lars Ljung
2013-01-27 2:24 ` Glenn Morris
2013-01-27 11:32 ` Lars Ljung
2021-07-15 9:01 ` Lars Ingebrigtsen
2021-07-30 11:54 ` Lars Ingebrigtsen
2021-07-31 2:40 ` Dmitry Gutov [this message]
2022-03-23 19:57 ` Lars Ingebrigtsen
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=265e7b3c-06c5-7fa4-81e4-0a75fea41765@yandex.ru \
--to=dgutov@yandex.ru \
--cc=13547@debbugs.gnu.org \
--cc=lars@matholka.se \
--cc=larsi@gnus.org \
--cc=monnier@iro.umontreal.ca \
--cc=rgm@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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.