On Wed, Feb 19, 2014 at 05:09:11PM +0200, Florin Avram wrote:
> Should I create a new issue regarding the error messages for this situation,
> or someone else does this?!
If you have time to do so that would be great. Thanks!
I'm glad we found out a common point of view. A better error message,
that indicates the cause (at least, in the provided example, it should
be very clear what is triggering the error), would definitely help save
some time, since no other command works to obtain other information
about this wor
On Wed, Feb 19, 2014 at 02:52:48PM +0200, Florin Avram wrote:
> I understand your point, but I have the feeling somewhere there is not a
> correct decision and things can be improved.
>
> What I'm trying to say is that what Subversion does in this case is not too
> obvious. Think to the following
I think I know enough about Subversion and work with it for more than 5
years, so I know very well what obstructed and missing means, and that
Subversion tries to not erase non-versioned data.I know only less about
new SVN 1.8.x behavior, which I'm testing currently, and which in some
situation
On Wed, Feb 19, 2014 at 12:17:06PM +, Philip Martin wrote:
> Stefan Sperling writes:
>
> > So, just move your file to a safe place, and run 'svn revert' again.
>
> In this case it's 'svn cleanup' after removing the obstruction.
Then I misunderstood the original problem report.
Can you give
Stefan Sperling writes:
> So, just move your file to a safe place, and run 'svn revert' again.
In this case it's 'svn cleanup' after removing the obstruction.
I suppose Subversion could check for such obstructions before creating
the workqueue item and fail with some sort of "cannot revert" err
On Wed, Feb 19, 2014 at 01:07:49PM +0200, Florin Avram wrote:
> Well, this design corrupts the working copy and I cannot use it after. I
> doubt this is what you want...
> I ran into this issue by testing how "svn revert" behaves on different
> strange situations, but, at least theoretically, anybo
Well, this design corrupts the working copy and I cannot use it after. I
doubt this is what you want...
I ran into this issue by testing how "svn revert" behaves on different
strange situations, but, at least theoretically, anybody can run into it.
On 19.02.2014 13:02, Stefan Sperling wrote:
On Wed, Feb 19, 2014 at 12:50:02PM +0200, Florin Avram wrote:
> Hi,
>
> I found a situation when using "svn revert" seems to corrupt the working
> copy. In a working copy like this:
> - wc_root_dir
> -- directory
> --- file
>
> erase the directory from disk (not using SVN) and create a file with
Hi,
I found a situation when using "svn revert" seems to corrupt the working
copy. In a working copy like this:
- wc_root_dir
-- directory
--- file
erase the directory from disk (not using SVN) and create a file with the
same name instead.
"svn status" will report:
~ directory
! directory/f
10 matches
Mail list logo
