Hi, I was about to file a bug report, I would like to hear your opinion
about svn resolve not complaining about wrong file names.
Basically, when resolving a conflict, you can do svn resolve --accept
working 'anything'
without having a clue on that the file was not there.
-- Andres
$ svn resolve
I've attached a file that creates a small repo that you can use to
reproduce this problem.
If you svnsync only the trunk of this repo, the new repo loses the
svn:special and svn:executable properties of files.
I ran into this with hgsubversion, but the bug is within svn itself: the
delta editor's
> -Original Message-
> From: Adam Mercer [mailto:ramer...@gmail.com]
> Sent: vrijdag 11 mei 2012 16:28
> To: users@subversion.apache.org
> Subject: Getting SVN E155035 after multiple updates of repository
>
> Hi
>
> I am trying to debug and problem with one of the repositories we host.