> -Original Message-
> From: Randy Martinez [mailto:randy.marti...@firstcontactent.com]
> Sent: Friday, April 27, 2018 1:35 AM
> To: users@subversion.apache.org
> Subject: unsubscribe
That's not going to work.
You can find instructions here:
https://subversion.apache.org/mailing-lists.
On Thu, 26 Apr 2018 13:48:18 -0400, Nico Kadel-Garcia
wrote:
>Bingo. It is, theoretically, possible to individually bring commits
>done directly on the slave back over to the original master to resolve
>such a resulting split brain.
And this is described in the svn-book too.
But when I set up m
On Thu, Apr 26, 2018 at 5:58 AM, Bo Berglund wrote:
> On Thu, 26 Apr 2018 11:26:38 +0200, OBones wrote:
>
>>Well, maybe I read this wrong, but the manual talks about a master and a
>>slave, which are tightly related. If I remove the master once the slave
>>is fully ready to take over its role, I'
I've figured it out. I just started a new job and I was trying to wrongly
merge a older branch into a newer branch that already had the old branches
revisions and that was how the exception was being generated.
On Thu, Apr 26, 2018 at 3:14 AM, Stefan Sperling wrote:
> On Wed, Apr 25, 2018 at 04:
On Wed, Apr 25, 2018 at 04:59:23PM -0700, Randy Martinez wrote:
> I'm on Tortoise SVN 1.10 and I'm getting this exception trying to resolve
> any merge conflict from a merge:
Unfortunately, we do not learn enough from the information provided
to independently reproduce this problem.
Can you expla
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
On Thu, 26 Apr 2018 11:26:38 +0200, OBones wrote:
>Well, maybe I read this wrong, but the manual talks about a master and a
>slave, which are tightly related. If I remove the master once the slave
>is fully ready to take over its role, I'm not sure it will work
>smoothly, hence my question.
I
Ryan Schmidt wrote:
On Apr 25, 2018, at 07:15, OBones wrote:
Nico Kadel-Garcia wrote:
In general, to jump that many major revisions, I tend to use "svnsync"
to allow the repositories to stay synchronized while the client stays
talking to the first repository, then take the first repository
ent
