[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Re: Seeking possible reason for error by diff -r PREV

From: John Szakmeister <john_at_szakmeister.net>
Date: Sat, 24 Oct 2009 05:44:32 -0400

On Thu, Oct 22, 2009 at 11:50 PM, Kotaro Murakami <kmurakami_at_collab.net> wrote:
> Thanks Stein.
> The svn version is 1.4.2 and the server is 1.4.0.
> I have not tried yet but "svn log --limit 1 file.cpp" will return r17535 since "--limit" just limits the number of lines displayed, no? Even so, in this case the COMMITTED should be r17535 (bcz "svn log file.cpp" prints r17535 first) and the PREV should be r16730 or r17534 like you said. I am not so sure which of the version svn takes for "diff -r PREV file.cpp" though.
> I would like to know a reason why this happens and to fix it if this happens because of a corrupted repository. Any ideas?

'svnadmin verify' or 'svnadmin dump' should help verify the integrity
of the repository. See what it says. I've seen a few revisions in
the past where a file was expected to be changed in a prior revision,
but the noderev and change entry was missing from that revision.



To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-24 11:45:44 CEST

This is an archived mail posted to the Subversion Users mailing list.