On 04.02.2014 14:51, Philip Martin wrote:
Florin Avram writes:
So, my question is: is this SVN 1.8 "svn delete" behavior intentional
or it should behave like with SVN 1.7 ?!
It was a result of a deliberate change in r1442611 to allow the delete
of unmodified copies without force:
svn cp
Florin Avram writes:
> So, my question is: is this SVN 1.8 "svn delete" behavior intentional
> or it should behave like with SVN 1.7 ?!
It was a result of a deliberate change in r1442611 to allow the delete
of unmodified copies without force:
svn cp iota iota2
svn rm iota2
--
Philip Mar
On 04.02.2014 14:06, Philip Martin wrote:
Stefan Sperling writes:
On Tue, Feb 04, 2014 at 11:49:24AM +0200, Florin Avram wrote:
Hi,
I noticed that SVN 1.8.5 does not give warnings for some situations, when
using "svn delete" (previously, using SVN 1.7.x, it did):
1. have a file replaced wit
Stefan Sperling writes:
> On Tue, Feb 04, 2014 at 11:49:24AM +0200, Florin Avram wrote:
>> Hi,
>>
>> I noticed that SVN 1.8.5 does not give warnings for some situations, when
>> using "svn delete" (previously, using SVN 1.7.x, it did):
>>
>> 1. have a file replaced with a directory in the worki
On Tue, Feb 04, 2014 at 11:49:24AM +0200, Florin Avram wrote:
> Hi,
>
> I noticed that SVN 1.8.5 does not give warnings for some situations, when
> using "svn delete" (previously, using SVN 1.7.x, it did):
>
> 1. have a file replaced with a directory in the working copy:
> - svn delete file
> - c
Hi,
I noticed that SVN 1.8.5 does not give warnings for some situations,
when using "svn delete" (previously, using SVN 1.7.x, it did):
1. have a file replaced with a directory in the working copy:
- svn delete file
- create new directory, with the same name as the file
- svn add file (the dir
