Uploaded image for project: 'Subversion'
  1. Subversion
  2. SVN-4468

'svn diff -c REV' picks the wrong revisions

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Invalid
    • 1.8.x
    • ---
    • libsvn_client
    • None

    Description

      While playing with some simple 'svn diff -cREV' invocations tonight, I found
      myself confused to find that the reported diffs were always between r0 and REV.
       Thinking I was nuts and that surely the test suite would have caught such a
      thing, I ran "diff_tests.py 9 -v", where I found amongst the output the following:
      
      {{{
      I: CMD: svn diff -c 3
      file:///home/cmpilato/projects/subversion/trunk/subversion/tests/cmdline/svn-test-work/repositories/diff_tests-9
      --config-dir
      /home/cmpilato/projects/subversion/trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config
      --password rayjandom --no-auth-cache --username jrandom
      I: <TIME = 0.012264>
      I: Index: A/B/T/phi
      I: ===================================================================
      I: --- A/B/T/phi	(revision 0)
      I: +++ A/B/T/phi	(revision 3)
      I: @@ -0,0 +1 @@
      I: +phi
      I: \ No newline at end of file
      I: CMD: svn diff -r 2:3 --config-dir
      /home/cmpilato/projects/subversion/trunk/subversion/tests/cmdline/svn-test-work/local_tmp/config
      --password rayjandom --no-auth-cache --username jrandom
      I: <TIME = 0.010389>
      I: Index: A/B/T/phi
      I: ===================================================================
      I: --- A/B/T/phi	(revision 0)
      I: +++ A/B/T/phi	(revision 3)
      I: @@ -0,0 +1 @@
      I: +phi
      I: \ No newline at end of file
      }}}
      
      Not only did 'svn diff -c 3' show a diff between r0 and r3, but the explicit
      'svn diff -r2:3' did the same!
      

      Attachments

        Activity

          People

            Unassigned Unassigned
            cmpilato C. Michael Pilato
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: