Two of my commits were immediately picked by LO. [1] [2]
Always nice to see, that down streaming still works for the fork... :-D
Regards,
Matthias
[1]
https://github.com/LibreOffice/core/commit/28dee1129c7a9c4da34b9253aefd6c6b2df1a073
[2]
https://github.com/LibreOffice/core/commit/9796738e11
Hello,
Am 15.01.19 um 19:42 schrieb Jim Jagielski:
> As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_OpenOffice"
>
> Notice the "_" :(
>
> I am guessing that's a dpg/deb restriction??
Does it mean it should build now?
I get with r1851505 from aoo42x branch:
. /usr/bin/fakeroot /us
Well, the error I was hitting is fixed, yeah.
You may need to blow away main/instsetoo_native/unxlngx6.pro/* and rebuild
> On Jan 17, 2019, at 9:32 AM, Mechtilde wrote:
>
> Hello,
>
> Am 15.01.19 um 19:42 schrieb Jim Jagielski:
>> As a reminder, w/ AOO 4.2.0, our Productname is now "Apache_Ope
Am 17.01.19 um 13:41 schrieb Matthias Seidel:
Two of my commits were immediately picked by LO. [1] [2]
Always nice to see, that down streaming still works for the fork... :-D
sure, better then to draw this on their own.
Again with a note who has tested and reviewed it - which is totally
fin
I just noticed that when including CatB components, beanshell
is not included in trunk/4.2.x but IS with 4.1.x
Any idea why the change?
-
To unsubscribe, e-mail: dev-unsubscr...@openoffice.apache.org
For additional commands, e-ma
Hi Marcus,
Am 17.01.19 um 20:42 schrieb Marcus:
> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>> Two of my commits were immediately picked by LO. [1] [2]
>>
>> Always nice to see, that down streaming still works for the fork... :-D
>
> sure, better then to draw this on their own.
>
> Again with
Hi Jim,
Am 16.01.19 um 22:36 schrieb Jim Jagielski:
> I just picked a number that was big... maybe just use 1 ? :)
1 worked, AOO4.5.0 Windows builds are now installable...
Regards,
Matthias
>
>> On Jan 16, 2019, at 3:58 PM, Matthias Seidel
>> wrote:
>>
>> Hi Jim,
>>
>> Am 09.01.1
The Question is:
Do we want to take action here or not?
On 17.01.19 21:19, Matthias Seidel wrote:
> Hi Marcus,
>
> Am 17.01.19 um 20:42 schrieb Marcus:
>> Am 17.01.19 um 13:41 schrieb Matthias Seidel:
>>> Two of my commits were immediately picked by LO. [1] [2]
>>>
>>> Always nice to see, that d
What action is there to take? It is a valid action by a downstream. Do we wish
they posted changes upstream? Yes! Can we require it? No!
Regards,
Dave
Sent from my iPhone
> On Jan 17, 2019, at 9:19 PM, Peter Kovacs wrote:
>
> The Question is:
>
> Do we want to take action here or not?
>
>