On 10/13/2016 2:54 PM, Stefan wrote: > On 10/12/2016 5:00 PM, 'Stefan Sperling' wrote: >> I'm actually surprised that we made this change in 1.7. >> >> If 'svn checkout' sees an existing directory the most likely situation is >> that the user has made a mistake. Leaving behind a working copy full of >> tree conflicts is hardly useful in this situation. I would expect this to >> happen only with a flag such as --force but the default behaviour being >> not touch an existing directory. > Was looking through the mailing list but couldn't find any older > discussion leading to this change of behavior in 1.7. > > From my point of view, it would be fine to change the behavior, if > checking out into an empty directory would still work without the > force-parameter. > Rational: New users of svn (especially Windows users) usually create a > folder first and then want to co into that directory (don't ask me why > it's different for the Linux user base). If an obvious "svn co [URL] > C:\mywc" fails without specifying the --force parameter it would > introduce a new unnecessary hurdle for new users, IMO.
Just wanted to check out whether the help string could be improved for 1.9 (and possibly 1.8). Doing a test checkout of the subversion trunk (svn co [url] .) into an unversioned copy of the subversion trunk I ended up with several files having been marked as deleted (tested with 1.9.4). Regards, Stefan
smime.p7s
Description: S/MIME Cryptographic Signature
