bug#20470: 24.5; VC log buffer no longer scrolls itself

[Stefan Monnier]

> How to reproduce: open a file checked out from RCS, hit C-x v l (or
> equivalently M-x vc-print-log RET) and notice that the cursor ends up at
> the start of the *vc-change-log* buffer. It should jump to the log
> message for the current revision, which was the case until the fix for
> bug #15322 "VC log buffer scrolls itself"

How far are the two positions?  What's between them?

> The particular revision control system doesn't really matter,

I'm beginning to suspect it does.  IIRC RCS (and CVS) put a bunch of
file-level metadata before the actual log, whereas other VCSes just put
the log right away.  So for RCS/CVS it might make sense to skip to the
first actual log message, so as to reproduce the behavior of
other backends.

Skipping to the log message corresponding to "the current revision"
seems much less important (and this is the part that was problematic
with the old behavior).


        Stefan