On 7/16/2016 01:48, Stefan wrote:
> Hi Tim,
>
> On 7/15/2016 21:49, Tim Tim wrote:
>> So, I have a most troubling issue: Intermittent blocking by our
>> pre-commit hook, with the only output being:
>>
>> svn: 'pre-commit' hook failed (did not exit cleanly: apr_exit_why_e
>> was 2, exitcode was -107
Hi Tim,
On 7/15/2016 21:49, Tim Tim wrote:
> So, I have a most troubling issue: Intermittent blocking by our
> pre-commit hook, with the only output being:
>
> svn: 'pre-commit' hook failed (did not exit cleanly: apr_exit_why_e
> was 2, exitcode was -1073741502). with no output.
>
> This hook is
So, I have a most troubling issue: Intermittent blocking by our
pre-commit hook, with the only output being:
svn: 'pre-commit' hook failed (did not exit cleanly: apr_exit_why_e
was 2, exitcode was -1073741502). with no output.
This hook is very simple: just checks that the log for the commit
co
On Jul 15, 2016, at 3:02, Stefan Sperling wrote:
> I'm afraid it's not obvious to me what issue you are referring to.
>
> Which behaviour are you expecting, and how does Subversion not meet
> your expectations?
I expect Subversion to merge only revisions 29203:HEAD of branchA into
branchB. Why
On Thu, Jul 14, 2016 at 09:38:05PM -0400, Alfred von Campe wrote:
> A user at work came to me with a strange merge issue and I have been able to
> reproduce it. This happens with both a 1.8.16 and 1.9.4 Linux CLI client. I
> usually can resolve these merge issues by deleting superfluous svn:mer
