On 14.03.2014 02:18, Jeb Wilson wrote:
>
> Hello,
>
>
>
> I’ve reproduced this mergeinfo overwriting issue using the following
> steps. We are seeing this with svn client v1.8.8, and using a remote
> VisualSVN server v2.7.0 (which uses svn v1.8.8). NOTE: This cannot be
> replicated by using a loc
Hello,
I've reproduced this mergeinfo overwriting issue using the following steps. We
are seeing this with svn client v1.8.8, and using a remote VisualSVN server
v2.7.0 (which uses svn v1.8.8). NOTE: This cannot be replicated by using a
locally created repo...we've only been able to replicate w
On 12.03.2014 21:24, Jeb Wilson wrote:
> Hello all,
>
> Apologies if this has already been reported, but it's a difficult one to
> search for. This came through from TortoiseSVN 1.8.5.
>
> Here's the basic way to reproduce:
>
> User #1 merges from A -> B and commits.
> User #2 merges SOMETHING ELS
Hello all,
Apologies if this has already been reported, but it's a difficult one to search
for. This came through from TortoiseSVN 1.8.5.
Here's the basic way to reproduce:
User #1 merges from A -> B and commits.
User #2 merges SOMETHING ELSE from A->B but doesn't update first to get User
#1's
