version control - Subversion oddity - svn info revision higher than last changed rev on project folder -


I'm not understood anything.

There is a working copy of my project - updated svn update (which says: update for the 18th amendment), I know that this is the latest when I click on the svn info < Code>, the amendment is 1895, but the last modified Rev 1888 is.

Inspecting logs using TortoiseSVN shows as 1888 final revision, there is no trace of 1895. In 1895 a svn log is empty, and between 1895 and 1888, a svn diff is also empty, that is, there is no difference.

How did I end up with some rogue amendments that have not really changed anything? It basically produces the build server (thinks it is in 1888) with my MSBuild SvnVersion function being out of sync (thinks the modification is 1895).

Any suggestions appreciated.

Edit: If the amendment will always show the latest amendments for the entire repository, it means that the SVN Varsian MSBuild function (which uses svnversion.exe but similar Things like showing behavior) do not show correct correction when you have a multi-project single repository, you will need to use "last modified Rev" for your version number.

As a result, now I have to do my own Swanleste Cheng Avevo MSBuild work roll.

This is not a problem or oddity ... the amendment number applies to the entire Subversion repository, and Therefore, the amendment number may be higher due to changes in the repository compared to the previous revision number, something changed in the branch of the repository on which you are working.

To clarify, if you are committed to trunk , to modify the repository to 10, and then the branches and Tags 1000, then "last modified amendment" for 10 trunk folder, but the current revision number of the entire repository will be 1000.


Comments

Popular posts from this blog

c# - How to capture HTTP packet with SharpPcap -

php - Multiple Select with Explode: only returns the word "Array" -

jquery - SimpleModal Confirm fails to submit form -