On Monday 06 June 2005 00:45, Max Bowsher wrote:
> Nicolas Goutte wrote:
> > On Sunday 05 June 2005 23:18, Max Bowsher wrote:
> >> Nicolas Goutte wrote:
> >>> I have a seen that Subversion has a problem with finding old revision of
> >>> a moved file, for example:
> >>> LANG=C svn log -r1
> >>> http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/ README
> >>> results in:
> >>> svn: REPORT request failed on
> >>> '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/ README'
> >>> svn: '/repos/svn/!svn/bc/1/branches/1.1.x-r14063/doc/README' path not
> >>> found
> >> That file does not exist in that revision. Thus a 'not found' error.
> >> Exactly as expected.
> > Well, it depends what you expect.
> > On one side a "svn log" gives such a revision number and when you want to
> > do
> > anything with that revision number it does not work. That is not what I
> > expect. Sorry!
> Well, no *I* don't expect svn log to give me revision numbers that don't
> work, either. But I'm pretty sure there is no way you could have got svn log
> to tell you that branches/1.1.x-r14063 existed in r1.
> I think you have tried to show us a minimal example of your problem, but
> have actually trimmed your actual problem away in trying to minimize the
> example, leaving behind a useless command.
Well, what about this then?
svn log http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
shows that there was a revision number 2558 on that file, right?
svn diff -r1:2558 http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
can even show you the patch of that revision.
Now, how do I get the log of that revision only?
svn log -r2558 http://svn.collab.net/repos/svn/branches/1.1.x-r14063/doc/README
svn: REPORT request failed on '/repos/svn/!svn/bc/2558/branches/1.1.x-r14063/doc/README'
svn: '/repos/svn/!svn/bc/2558/branches/1.1.x-r14063/doc/README' path not found
Why does "svn log" show a revision, and a log, which can't be retrieved independently
with svn log -r<rev> ? I know that the file moved since that revision, but that's
a detail that one usually doesn't care about when looking at history. If I want to
know why a given change was made, it doesn't matter to me where the file was when
that change was made.
This problem affects KDE a lot, because everything got moved (reorganized)
after the cvs2svn conversion, so any trip back in history hits this "no such revision" bug
in svn log -r.
David Faure, email@example.com, sponsored by Trolltech to work on KDE,
Konqueror (http://www.konqueror.org), and KOffice (http://www.koffice.org).
To unsubscribe, e-mail: firstname.lastname@example.org
For additional commands, e-mail: email@example.com
Received on Fri Jun 10 14:21:45 2005