subversion-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bert Huijben" <>
Subject RE: [BUG] svn update produces unexpected result
Date Mon, 13 Mar 2017 08:14:01 GMT
The last change revision is documented to be the last revision in which that
node changed. 


The revision number in Subversion is global for the repository, so not
changing every file in every revision is 100% expected behavior. And this is
the reason we show these different revisions.


See the Subversion documentation for the fine details. (E.g. )


The help from --revision shows that we have even more interesting revisions
tied to a file:

-r [--revision] ARG      : ARG (some commands also take ARG1:ARG2 range)

                             A revision argument can be one of:

                                NUMBER       revision number

                                '{' DATE '}' revision at start of the date

                                'HEAD'       latest in repository

                                'BASE'       base rev of item's working copy

                                'COMMITTED'  last commit at or before BASE

                                'PREV'       revision just before COMMITTED






From: Deng, Xiao [] 
Sent: vrijdag 10 maart 2017 19:48
Subject: [BUG] svn update produces unexpected result




When using svn update on a file with -r flag from one revision to another
where the content of the file at both revisions are identical, the last
commit of result file appears to be out of sync. 



Foo.txt have identical content at r100 and r200

Foo.txt is at base revision r100

svn update Foo.txt -r200

svn status Foo.txt -v --xml


                base revision === last commit revision === 200


                base revision === 200 !== last commit revision === 100


Best Regards,


Xiao Deng

Software Engineer 2

Aviation | Garmin International




CONFIDENTIALITY NOTICE: This email and any attachments are for the sole use
of the intended recipient(s) and contain information that may be Garmin
confidential and/or Garmin legally privileged. If you have received this
email in error, please notify the sender by reply email and delete the
message. Any disclosure, copying, distribution or use of this communication
(including attachments) by someone other than the intended recipient is
prohibited. Thank you.

View raw message