On Sun, Dec 4, 2016 at 7:07 PM, Olaf van der Spek <ml_at_vdspek.org> wrote:
> On Sun, Dec 4, 2016 at 6:27 PM, Johan Corveleyn <jcorvel_at_gmail.com> wrote:
>> On Sun, Dec 4, 2016 at 11:32 AM, Olaf van der Spek <ml_at_vdspek.org> wrote:
>> So do you agree that the --force behaviour (just blindly incorporating
>> local files, without any warning) should *not* be the default?
>
> I'm not sure..
> Why can't it be the default for directories?
I don't understand what you're trying to say here. There are always
files involved, no? I don't care about the directories themselves in
this case. I'm talking about the --force behaviour of "incorporating"
existing files to make them part of a checkout that's being checked
out over an existing tree.
> How often does such an accidental checkout happen anyway?
I have no idea. I suppose it happens from time to time. But in any
case this discussion is a bit pointless ... we won't change the
default "non-forcing" behaviour of 'svn checkout', simply because it's
breaking backwards compatibility. If we want to improve the experience
for users, we should work on improved tree conflict resolving (as is
currently being worked on for 1.10 --- help is most welcome :-).
> What about checking whether the destination directory exists before
> the checkout and confirming the checkout is desired if it does exist
> already?
Yep, that's a good suggestion. As a matter of fact, Patrick Steinhardt
is currently working on something like this. See this dev@ mail [1]
with his latest patch. You might want to take a look (the commit
message in the mail contains a good description of the behaviour).
[1] https://lists.apache.org/thread.html/9ef6d2351c01865ba2e96537fb7b4aa3ff1752b1ace7dd4a95a4e151@%3Cdev.subversion.apache.org%3E
--
Johan
Received on 2016-12-05 00:52:14 CET