Hi again;
On 2020-01-04 05:16, Matthias Seidel wrote:
> Hi Pedro,
>
> Thanks!
>
> Unfortunately the build process just stops at some point (on Windows),
> no error codes I could give you.
The problems are usually related to getting the patches applied
correctly. There can be no hunks or mismatche
+1
> On Jan 8, 2020, at 9:02 PM, Patricia Shanahan wrote:
>
> On 1/8/2020 5:55 PM, Dave Fisher wrote:
>> Hi -
>> See inline
>> Sent from my iPhone
>>> On Jan 8, 2020, at 3:44 PM, Peter Kovacs wrote:
>>>
>>> Hello again,
>>>
>>> hope I do not annoy anyone, with my questions.
>>> I have looked
Hi Jim,
Am 08.01.20 um 14:42 schrieb Jim Jagielski:
>> On Jan 7, 2020, at 11:35 AM, Matthias Seidel
>> wrote:
>>
>> Back to the topic:
>>
>> Personally I don't see a reason for a 4.1.8 dev release.
>> It is only a micro update and I do build test versions (for Windows) on
>> a regular base [1].
At least checking bz and documenting the findings should be done.
And the refactoring I want to do. I already know how the code should look like.
Am 9. Januar 2020 10:57:46 MEZ schrieb Patricia Shanahan :
>What happens if you ignore the assertion and carry on?
>
>I had to do that for several as
What happens if you ignore the assertion and carry on?
I had to do that for several assertions when debugging some security
problems - the problems I was working were higher priority.
On 1/9/2020 1:35 AM, Peter Kovacs wrote:
Hi,
To be clear the Assert is a different issue and needs more rese
Hi,
To be clear the Assert is a different issue and needs more research.
The Assert claims a different object is to be used for top level objects. Since
the issue pops up on top-level object, right at start, I assume something is
not as it should be designed. The answers on the list suggest tha
