Hi,
Recently we have been having multiple instances of a problem that doesn't seem
to be going away. The easiest way to see it is to reproduce the following steps.
1) check out a working copy of one of our development branches:
svn co svn://svn.nublado.org/cloudy/branches/backtrace
Changes f
On Thu, Oct 27, 2016 at 12:14 PM, Peter van Hoof wrote:
> Hi,
>
> Recently we have been having multiple instances of a problem that doesn't
> seem to be going away. The easiest way to see it is to reproduce the
> following steps.
>
> 1) check out a working copy of one of our development branches:
Hi Johan,
On 2016-10-28 16:16, Johan Corveleyn wrote:
On Thu, Oct 27, 2016 at 12:14 PM, Peter van Hoof wrote:
Hi,
Recently we have been having multiple instances of a problem that doesn't
seem to be going away. The easiest way to see it is to reproduce the
following steps.
1) check out a wor
On Thu, Nov 03, 2016 at 12:49:26PM +0100, Peter van Hoof wrote:
> I am not even sure how you can commit changes without committing mergeinfo.
> As far as I know that is all automatic.
The designers of SVN's merge-tracking decided to re-use the existing
versioned SVN properties to store mergeinfo,
Hi Peter,
On 11/3/2016 12:49, Peter van Hoof wrote:
> Hi Johan,
>
> On 2016-10-28 16:16, Johan Corveleyn wrote:
>> On Thu, Oct 27, 2016 at 12:14 PM, Peter van Hoof
>> wrote:
>>> Hi,
>>>
>>> Recently we have been having multiple instances of a problem that
>>> doesn't
>>> seem to be going away. Th
Hi,
I have been sidetracked by other work for a while, but would like to get
back to this now...
I double-checked this and checked out the branch at r8689. This is the result
% svn co svn://svn.nublado.org/cloudy/branches/backtrace@8689
% cd backtrace/
% svn proplist --verbose source/
[..
