The online doco has some examples:
http://svnbook.red-bean.com/nightly/en/svn.ref.svnversion.re.html
A mixed revision is where the directory and it's
subdirectories are in a state where they have multiple
revisions.
So, Directory A was updated at revision 1. I go into
a child directory and update it so it's now reflecting
revision 2. If I haven't updated Directory A, it will
still only have been updated at Revision 1.
And, if you look at the help for svnversion, the -c
instructs the command to use the "last changed rather
than the current"
Also, to continue the docu you quoted...
The version number will be a single number if the
working
copy is single revision, unmodified, not switched
and with
an URL that matches the TRAIL_URL argument. If the
working
copy is unusual the version number will be more
complex:
4123:4168 mixed revision working copy
4168M modified working copy
4123S switched working copy
4123:4168MS mixed revision, modified, switched
working copy
So, you've just come across a working copy which has a
complex version number. That's all.
>Hmm... OK, this wasn't clear. The documentation says:
>
> The version number will be a single number if the
working
> copy is single revision, unmodified, not switched
and with
> an URL that matches the TRAIL_URL argument.
>
>but I didn't think that "single revision" was
referring to last
>changed revisions too.
____________________________________________________
Do you Yahoo!?
Never miss an Instant Message - Yahoo! Messenger for SMS
http://au.mobile.yahoo.com/mweb/index.html
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Sun Jan 15 23:23:18 2006