Thread

Posted on Fri Apr 7 19:17:15 2006 by mikekonikoff
diff output vs. actual repository revision
I'm viewing the revision log for a file in my Subversion repository using SVN::WEB. It shows the changes between revision 394 and the previous revision of the file (379). The programmer who checked in the changes agrees that what SVN::WEB shows in the revsion log matches her recollection of what she changed in the file and committed to the repository. No other revisions on the file have been committed; 379 was the initial copy of the trunk into a branch, and 394 was the only revision to be committed on the file in that branch.

However, when I check out revision 394 from the repo, none of the changes reported by SVN::WEB are actually in the file.

How is it possible that the file at revision 394 does not reflect what SVN::WEB shows are the differences between 394 and 379? The changes are significant and non-trivial, not just whitespace or indentation. I'm talking about dozens of new lines of code being added, and dozens of old lines being deleted. Furthermore, TortoiseSVN correctly reports the differences between the two revisions.

Is this a bug in SVN::WEB? Are diff outputs cached somewhere?

Mike
Direct Responses: 2120 | 2241 | Write a response
Posted on Fri Apr 7 19:21:48 2006 by mikekonikoff in response to 2119
Re: diff output vs. actual repository revision
Just a point of clarification, when I say "TortoiseSVN correctly reports the differences between the two revisions" I mean that when I checkout and compare these two revisions locally, the actual differences between the two revisions match what is reported in TortoiseSVN, unlike what is reported by SVN::WEB.
Write a response
Posted on Sat May 6 18:56:49 2006 by nikc in response to 2119
Re: diff output vs. actual repository revision

That's decidedly odd.

Just to rule out obvious errors, you say that the changes happened on a branch. You're quite sure that when you checked the file out you checked out the copy on the branch, not the trunk, right?

I don't check this forum very often, so if you reply, please do so direct to me, nikc@cpan.org.

N

Write a response