Hi,
I am not sure how Update To Revision is intended to work, only how I would
like it to work :-) I would like it to do what the manual says: "update your
working copy to a specific revision"
Here is how it works:
(1) If my WC is up to date:
- After Update To Revision (#): files and directory structure reflect rev #
(2) If I have a file in my WC which has not been added+committed to
repository:
- After Update To Revision (#): files and directory structure reflects rev #
except that the not-added file is still there
(3) If I have a file with changes that has not been committed:
- After Update To Revision (#): files and directory structure reflects rev #
except that the not-committed file is merged with rev # of the file.
(1) is beautiful and I understand that (2) and (3) happens since TSVN cannot
allow information to get lost. However, especially (3) makes your WC a mess,
imho.
Unless (2) and (3) are intended, I suggest that you can only Update To
Revision if your WC (exactly) reflects a revision in the repository. If you
try to Update To Revision when WC does not reflect a revision in the
repository, you should be told to update/commit/revert before Update To
Revision can take place.
I think the manual needs an update since it says "update your working copy
to a specific revision":
- If my suggestion is rejected:
that is not what happens in (2) and (3).
If my suggestion is accepted:
- The manual should say that you need to revert/update/commit (if necessary
and you are working on the HEAD revision) or revert if you are working on a
not-HEAD revision (for some odd reason) before you can make a Update To
Revision.
All the best
Roland
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Oct 26 11:59:52 2004