Originally created by: mar...@v.loewis.de
Originally owned by: cmpilato
Since Subversion 1.5, co has a --force option that deals with pre-existing
files. Subversion's processing is somewhat counter-intuitive at first
glance, hence it is desirable to elaborate in the book.
IIUC, without --force, co will give up if WC files conflict with
preexisting files. With --force, it does *not* overwrite the existing files
(which would be the intuitive thing to expect). Instead, it reports the 'E'
status, and leaves the original file as-is. As a consequence, the original
file appears as a modification to the WC. I believe (but don't know for
sure) that the motivation for this behavior is that it is then the choice
of the user to revert all changes right away (thus overwriting the original
files), or to edit/commit the original files (thus having them take
precedence over the repository files) - the co command itself makes no choice.
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
(No comment was entered for this change.)
Labels: -Type-Enhancement Type-Defect Milestone-en-1.6
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
(No comment was entered for this change.)
Owner: cmpilato
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
(No comment was entered for this change.)
Summary: 'svn checkout --force' option and E code not explained
View and moderate all "tickets Discussion" comments posted by this user
Mark all as spam, and block user from posting to "Tickets"
Originally posted by: cmpilato
FIXED:
Sending book/ch09-reference.xml
Transmitting file data .
Committed [r3906].
Status: Fixed