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

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

From: Stein Somers <ssomers_at_opnet.com>
Date: Fri, 23 Oct 2009 13:07:17 +0200

I wrote:
> if "svn log file.cpp -l 1" prints r17535 as the
> last change, then PREV for that file is r17534

Wrong. The first log entries may show branching, or in general the copying of
a parent directory of file.cpp. How you can locate direct changes on file.cpp
with "svn log", I don't know. I guess "svn log file.cpp -v" and find the
direct change in the change list. Incidentally, "svn log -r COMMITTED
configure_at_HEAD" doesn't work for me either, but I guess svn log simply
doesn't bother to trace the path from the peg revision.

"svn info -r COMMITTED file.cpp" is probably the quickest way and works fine
for me, both on svn 1.6.5 and 1.4.2. As does "svn diff -r PREV file.cpp".

Barring wiser advise on the list, I think your repository is corrupt. I would
"svnadmin dump" and load it somewhere else to figure that out.

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subversion.tigris.org].
Received on 2009-10-23 13:08:14 CEST

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