all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Dmitry Gutov <dgutov@yandex.ru>
Cc: Glenn Morris <rgm@gnu.org>, Lars Ljung <lars@matholka.se>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	13547@debbugs.gnu.org
Subject: bug#13547: svn annotate - incorrect previous/next revision
Date: Wed, 23 Mar 2022 20:57:09 +0100	[thread overview]
Message-ID: <874k3o788a.fsf@gnus.org> (raw)
In-Reply-To: <265e7b3c-06c5-7fa4-81e4-0a75fea41765@yandex.ru> (Dmitry Gutov's message of "Sat, 31 Jul 2021 05:40:37 +0300")

Dmitry Gutov <dgutov@yandex.ru> writes:

> 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.

This was half a year ago, and nobody's piped up, so I'm closing this bug
report.  (If somebody that uses svn wants this feature, they can
resurrect the patch, probably.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





      reply	other threads:[~2022-03-23 19:57 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
2022-03-23 19:57           ` Lars Ingebrigtsen [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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874k3o788a.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=13547@debbugs.gnu.org \
    --cc=dgutov@yandex.ru \
    --cc=lars@matholka.se \
    --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.