On Fri, 4 Dec 2009 07:00:43, K F <cmkforce_at_yahoo.com
> We have run into a situation where we have a duplicate
> revision number. The problem that occurred is that when a new tag was
> it was thought that it was being made from revision 74 off of the
> trunk and in
> reality it was made from revision 74 off of a previous tag.(attachment 1)
> Hovering over the rev 74 off the tag reveals that it is a
> copy (of rev 68). (attachment 2)
> I did not create the tag off of the tag, or create the copy
> so I am not sure what happened at this point.
The tag AOL_2.0.4_GA was created in r77. Howering
over the node will tell you the user name, i.e. the one to
"blame" for the mistake.
> I am just curious why there are
> two rev 74s? Any insight would be appreciated.
It's the "Exact copy sources" option (also causing the
white square boxes). When active, this option will not
use the latest change (rev 68 in your case) as the copy
source. Instead it will report exactly, what the log
command returns as "copy-from-revision".
That revision can basically be any from 68 upward
(all of them are equivalent wrt. to their content).
If you used the repository browser and it happened
to display rev 74 when the copy was made, this
will most likely be the source copy revision.
Another way to have the same revision show up
more than one is by modifying multiple copies / branches
in the same revision. Then, the change, i.e. revision,
must be shown in all these branches.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2009-12-05 01:34:23 CET