Hi Chris,
> Create a file, give it some content, check it in.
> Change it, commit
> Rename, commit
> Compare With -> Base Version
>
> You will see that it reports "No Differences"
That's as expected. Base Version is the pristine version in the working
copy - i.e. the last thing sent to or received from the server. You've
just done a commit, so the base version is what you just committed.
There are several reasons for having Base Version as well as Latest from
repository
- you don't need to go across the network, because the pristine
copy is held locally
- hence you can compare with Base Version without network access
(on the train, for example)
- you may want to see what changes you have made, without the
confusion of later checkins
- you may not be working against the latest in the repository
(maybe you've rolled back a bit to try to remind yourself
how the code behaved 3 checkins ago when it was definitely
working and want to try a different path)
To compare against the version before your refactoring, you would need
compare with revision... but Subversion itself doesn't handle history
across renames perfectly yet and compare is one area which suffers.
It's a known issue, along with merge tracking, and will be solved in a
future version (though they haven't yet said which or when).
I hope this clarifies things. Note, I have nothing to do with either
project other than being an (almost) satisfied user. Thanks for the
Properties sheet guys! It's a great addition for us, since we use
svn:externals quite a lot.
Cheers,
Ian Brockbank
Senior Applications Software Engineer
e: ian.brockbank@wolfsonmicro.com / apps@wolfsonmicro.com
scd: ian@scottishdance.net
t: +44 131 272 7145
f: +44 131 272 7001
Received on Fri Jul 23 19:18:41 2004