When I first started using svnmucc, it used to be the case that
svnmucc 'put' --revision 0 would fail if the target file already
existed. This no longer happens.
The previous behaviour was very useful, so are there any plans to reinstate it?
I don't think there is a straightforward way to guarant
sebb wrote on Tue, 07 Jul 2020 12:55 +0100:
> Is there any restriction on svnmucc targets which can appear in a batch
> script?
>
> I assume that all targets must be in the same repository, but are
> there any further restrictions, e.g. must they have the same initial
> root directory path?
>
>
Is there any restriction on svnmucc targets which can appear in a batch script?
I assume that all targets must be in the same repository, but are
there any further restrictions, e.g. must they have the same initial
root directory path?
I ask this because I am getting the following:
svnmucc: E175
Hi
Yeah, I linked to that issue in my first mail since I thought it could be
related also, but reading that ticket I thought it didn't exactly match my
issue. I guess I'll have to retry once that fix gets released.
Regards,
Mikael
Från: Stefan Sperling
Skickat:
On Tue, Jul 07, 2020 at 09:01:50AM +, Mikael Stålhammar wrote:
> Hi
> I'm having an issue with merging/releasing a feature branch to trunk, getting:
>
>
> --- Recording mergeinfo for merge between repository URLs into '.':
>
> svn: E155023: Can't set properties on
> 'E:\SVN\WorkingCopies\re
Hi
I'm having an issue with merging/releasing a feature branch to trunk, getting:
--- Recording mergeinfo for merge between repository URLs into '.':
svn: E155023: Can't set properties on
'E:\SVN\WorkingCopies\repo\trunk\folder\file.txt': invalid status for updating
properties.
The background
