Re: branches/gbuild-reintegration merge?

Damjan Jovanovic wrote: On Sat, Mar 26, 2016 at 12:11 PM, Andrea Pescetti wrote: you fixed them "while at it" or are they side effects of the build system changes? Those bug fixes were present in the original gbuild branch - they're not something I developed. I don't know why. OK, thanks for

Re: branches/gbuild-reintegration merge?

On Sat, Mar 26, 2016 at 12:11 PM, Andrea Pescetti wrote: > On 22/03/2016 Damjan Jovanovic wrote: >> >> For the past month I've been working on preparing the gbuild branch >> for merge into trunk, and I believe it to be essentially ready. > > > Thank you Damjan, this is one of

Re: branches/gbuild-reintegration merge?

On 22/03/2016 Damjan Jovanovic wrote: For the past month I've been working on preparing the gbuild branch for merge into trunk, and I believe it to be essentially ready. Thank you Damjan, this is one of the best news about project development we've had in recent months! And I won't insist

Re: branches/gbuild-reintegration merge?

Am 03/25/2016 06:48 AM, schrieb Pedro Giffuni: Since people are asking … The changes from the time Damjan branched are: - Removal of an unused file. - Removal of non-existing writerperfect files from the Rat scan - A security patch for graphite. - Flags to fix building with newer system boost:

Re: branches/gbuild-reintegration merge?

Since people are asking … The changes from the time Damjan branched are: - Removal of an unused file. - Removal of non-existing writerperfect files from the Rat scan - A security patch for graphite. - Flags to fix building with newer system boost: this doesn’t affect the internal boost and have

Re: branches/gbuild-reintegration merge?

Am 03/23/2016 05:22 PM, schrieb Pedro Giffuni: In response to Marcus; For furture releases we should think about to decrease limits, e.g., introduce newer baseline requirements for the OS. However, this is not for the current release line (4.x). It would be uncommon to do such kind of changes

RE: branches/gbuild-reintegration merge?

rcus.m...@wtnet.de] > Sent: Tuesday, March 22, 2016 16:37 > To: dev@openoffice.apache.org > Subject: Re: branches/gbuild-reintegration merge? > [ ... ] > > wow and \o/ . Thats great news. :-) > > As non-coder I've not the biggest inside and knowledge. However, I'm > still afra

Re: branches/gbuild-reintegration merge?

On Tue, Mar 22, 2016 at 12:08 PM, Damjan Jovanovic wrote: > Hi > > For the past month I've been working on preparing the gbuild branch > for merge into trunk, and I believe it to be essentially ready. > > My work can be found in branches/gbuild-reintegration which started as >

Re: branches/gbuild-reintegration merge?

In response to Marcus; For furture releases we should think about to decrease limits, e.g., introduce newer baseline requirements for the OS. However, this is not for the current release line (4.x). It would be uncommon to do such kind of changes with the next release. I am not really think

Re: branches/gbuild-reintegration merge?

Am 03/22/2016 08:08 PM, schrieb Damjan Jovanovic: Hi For the past month I've been working on preparing the gbuild branch for merge into trunk, and I believe it to be essentially ready. My work can be found in branches/gbuild-reintegration which started as a branch of trunk to which all patches

Re: branches/gbuild-reintegration merge?

Am 03/22/2016 09:08 PM, schrieb Pedro Giffuni: +1 I have been following the branch and it looks well. Also, ydario@ was contacted about the OS/2 builds and I am sure he will catch up. I did most of the illumos changes that I considered portable enough and didn't break tests so I think they

Re: branches/gbuild-reintegration merge?

+1 I have been following the branch and it looks well. Also, ydario@ was contacted about the OS/2 builds and I am sure he will catch up. I did most of the illumos changes that I considered portable enough and didn't break tests so I think they will catch up too. For a future wishlist (yeah

branches/gbuild-reintegration merge?

Hi For the past month I've been working on preparing the gbuild branch for merge into trunk, and I believe it to be essentially ready. My work can be found in branches/gbuild-reintegration which started as a branch of trunk to which all patches from branches/gbuild patches were gradually merged,