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

move-update not setting last_mod_time in destination

    XMLWordPrintableJSON

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: trunk
    • Fix Version/s: 1.8.0
    • Component/s: libsvn_wc
    • Labels:
      None

      Description

      svnadmin create repo
      svn import -mm repo/format file://`pwd`/repo/A/f
      svnmucc -mm put repo/README.txt file://`pwd`/repo/A/f
      svn co file://`pwd`/repo wc
      svn mv wc/A wc/A2
      
      A/f and A2/f both have last_mod_time set, that's OK. (Perhaps we should remove
      last_mod_time from the deleted A/f but that's not the bug here.)
      
      svn up --accept postpone -r1 wc
      
      A/f has lost_mod_time cleared, thats OK.  A2/f unchanged and still has
      last_mod_time.
      
      svn resolve --accept mc wc/A
      
      A2/f has last_mod_time cleared, that's a bug.  It means the client will have to
      do a full-text comparison to detect differences.
      

        Attachments

          Activity

            People

            • Assignee:
              Unassigned
              Reporter:
              philipm Philip Martin
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: