Re: Adopting unversioned directory on svn up

2016-12-04 Thread Johan Corveleyn
On Sun, Dec 4, 2016 at 7:07 PM, Olaf van der Spek wrote: > On Sun, Dec 4, 2016 at 6:27 PM, Johan Corveleyn wrote: >> On Sun, Dec 4, 2016 at 11:32 AM, Olaf van der Spek wrote: >> So do you agree that the --force behaviour (just blindly incorporating >> local files, without any warning) should *no

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Johan Corveleyn
On Sun, Dec 4, 2016 at 10:17 PM, Daniel Shahaf wrote: > Johan Corveleyn wrote on Sun, Dec 04, 2016 at 18:27:48 +0100: >> It's impossible to say now which files were there before, and which >> were added by the checkout (OK, the unversioned items were certainly >> "local files", but the versioned o

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Daniel Shahaf
Johan Corveleyn wrote on Sun, Dec 04, 2016 at 18:27:48 +0100: > It's impossible to say now which files were there before, and which > were added by the checkout (OK, the unversioned items were certainly > "local files", but the versioned ones ... who knows? Couldn't you look for files and empty di

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Olaf van der Spek
On Sun, Dec 4, 2016 at 6:27 PM, Johan Corveleyn wrote: > On Sun, Dec 4, 2016 at 11:32 AM, Olaf van der Spek 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

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Stefan Sperling
On Sun, Dec 04, 2016 at 11:32:47AM +0100, Olaf van der Spek wrote: > On Sun, Dec 4, 2016 at 1:04 AM, Johan Corveleyn wrote: > > I think the most annoying consequence of accidentally checking out > > over an existing directory, without any conflict detection (if the > > --force behaviour would be t

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Johan Corveleyn
On Sun, Dec 4, 2016 at 11:32 AM, Olaf van der Spek wrote: > On Sun, Dec 4, 2016 at 1:04 AM, Johan Corveleyn wrote: >> I think the most annoying consequence of accidentally checking out >> over an existing directory, without any conflict detection (if the >> --force behaviour would be the default)

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Stefan Sperling
On Sat, Dec 03, 2016 at 10:11:49PM +0100, Olaf van der Spek wrote: > On Sat, Dec 3, 2016 at 10:07 PM, Stefan Sperling wrote: > > On Sat, Dec 03, 2016 at 06:42:11PM +0100, Olaf van der Spek wrote: > >> On Tue, Nov 29, 2016 at 10:19 PM, Stefan Sperling wrote: > >> >> >> For directories it seems lik

Re: Adopting unversioned directory on svn up

2016-12-04 Thread Olaf van der Spek
On Sun, Dec 4, 2016 at 1:04 AM, Johan Corveleyn wrote: > I think the most annoying consequence of accidentally checking out > over an existing directory, without any conflict detection (if the > --force behaviour would be the default), would be that you cannot > easily undo the operation. You have