On Thu, Apr 26, 2018 at 12:11:46PM +0200, Stefan Sperling wrote:
> On Thu, Apr 26, 2018 at 06:44:25AM +, Chris wrote:
> > Hi again,
> >
> > I'm attaching a script that reproduces the behavior of checking revisions
> > before the branch was created as well as going back to the revision before
On Thu, Apr 26, 2018 at 06:44:25AM +, Chris wrote:
> Hi again,
>
> I'm attaching a script that reproduces the behavior of checking revisions
> before the branch was created as well as going back to the revision before
> the file was created on trunk.
Thank you Chris!
I have filed https://i
t give access to the
company-internal repo to test the actual problem.
TIA,
Chris
On Wed, 4/25/18, Chris wrote:
Subject: Re: Surprising behavior with 1.10 tree conflict resolver
To: "Chris" , "Stefan Sperling"
Cc: users@subve
ure to repeat it in a simple script).
/Chris
On Wed, 4/25/18, Stefan Sperling wrote:
Subject: Re: Surprising behavior with 1.10 tree conflict resolver
To: "Chris"
Cc: users@subversion.apache.org
Date: Wednesday, April 25, 2018, 1:37 P
On Wed, Apr 25, 2018 at 11:04:13AM +, Chris wrote:
> I'm trying out subversion 1.10 and it's going both good and bad.
>
> The good thing is that new interactive conflict resolver works absolutely
> brilliantly for text conflicts. Great job everyone!
> The bad news is that I can't resolve my t
I'm trying out subversion 1.10 and it's going both good and bad.
The good thing is that new interactive conflict resolver works absolutely
brilliantly for text conflicts. Great job everyone!
The bad news is that I can't resolve my tree conflicts.
Let me prefix this with saying that the corporate
