On Thu, 2012-10-18 at 16:05 -0500, Alexandro Colorado wrote:
Recently i reported a 7yr old bug on memory management, i am sure LibO
also inherit that bug and they haven't fix it mainly because of the
low level technical knowledge to devote to the performance project.
I seem to
Hi Alexandro,
On Mon, 2012-10-22 at 03:17 -0500, Alexandro Colorado wrote:
On Sat, Oct 20, 2012 at 2:39 AM, Michael Meeks michael.me...@suse.comwrote:
On Thu, 2012-10-18 at 16:05 -0500, Alexandro Colorado wrote:
Recently i reported a 7yr old bug on memory management, i am sure LibO
also
On 14/10/2012 Eike Rathke wrote:
On Saturday, 2012-10-13 18:07:24 -0700, Pedro Giffuni wrote:
This said, the latest versions of LO introduce bugs that I can't
reproduce on AOO. AOO is very stable and we want to keep it that way.
Thanks. The latest version of AOO also still didn't fix bugs that
On 10/18/12, Andrea Pescetti pesce...@apache.org wrote:
On 14/10/2012 Eike Rathke wrote:
On Saturday, 2012-10-13 18:07:24 -0700, Pedro Giffuni wrote:
This said, the latest versions of LO introduce bugs that I can't
reproduce on AOO. AOO is very stable and we want to keep it that way.
Thanks.
Just IMHO;
- Original Message -
From: Alexandro Colorado j...@oooes.org
...
Then what I'd like to say, speaking from my personal point of view of
course, is that we could make millions of users happier by sharing
bugfixes (not necessarily features).
Sharing bugfixes would be
In my humble opinion it should be possible to have a shared code base,
shared bug fixing but separate features !!
When big companies like SAP, IBM and firmer SUN can do what, it should be
soo much easier for us, being all volunteers working with one goal, to make
quality software free of roalties
Hi Pedro,
On Saturday, 2012-10-13 18:07:24 -0700, Pedro Giffuni wrote:
This said, the latest versions of LO introduce bugs that I can't
reproduce on AOO. AOO is very stable and we want to keep it that way.
Thanks. The latest version of AOO also still didn't fix bugs that are
fixed since long
Hello,
From: Eike Rathke [mailto:o...@erack.de]
What I want to say is that we're getting nowhere with
pointing fingers.
yes, indeed.
Only this is not a one-way street.
For example, i will never forget what the FSF said against AOO:
http://www.fsf.org/news/openoffice-apache-libreoffice
--- Dom 14/10/12, Eike Rathke ha scritto:
Hi Pedro,
On Saturday, 2012-10-13 18:07:24 -0700, Pedro Giffuni
wrote:
This said, the latest versions of LO introduce bugs
that I can't
reproduce on AOO. AOO is very stable and we want to
keep it that way.
Thanks. The latest version of
On 10/14/2012 06:08 AM, Eike Rathke wrote:
Hi Pedro,
On Saturday, 2012-10-13 18:07:24 -0700, Pedro Giffuni wrote:
This said, the latest versions of LO introduce bugs that I can't
reproduce on AOO. AOO is very stable and we want to keep it that way.
Thanks. The latest version of AOO also
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO
and LO would not be overly complicated (bad memory, but maybe it was Tom
Davis referencing the fact that Symphony was kept in sync with OOo). Are
any changes integrated between AOO and LO (in either
On Sat, Oct 13, 2012 at 6:48 PM, Andrew Douglas Pitonyak
and...@pitonyak.org wrote:
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO and
LO would not be overly complicated (bad memory, but maybe it was Tom Davis
referencing the fact that Symphony
Hi Andrew,
Andrew Douglas Pitonyak schrieb:
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO
and LO would not be overly complicated (bad memory, but maybe it was Tom
Davis referencing the fact that Symphony was kept in sync with OOo).
Such
Hi Andrew;
- Original Message -
...
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO and
LO
would not be overly complicated (bad memory, but maybe it was Tom Davis
referencing the fact that Symphony was kept in sync with OOo). Are
On 10/13/2012 07:07 PM, Rob Weir wrote:
On Sat, Oct 13, 2012 at 6:48 PM, Andrew Douglas Pitonyak
and...@pitonyak.org wrote:
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO and
LO would not be overly complicated (bad memory, but maybe it was Tom
On 10/13/2012 07:20 PM, Regina Henschel wrote:
Hi Andrew,
Andrew Douglas Pitonyak schrieb:
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO
and LO would not be overly complicated (bad memory, but maybe it was Tom
Davis referencing the fact that
On 10/13/2012 09:07 PM, Pedro Giffuni wrote:
Hi Andrew;
- Original Message -
...
Couple of questions:
(Q) it was stated to me at one time that integrating changes between AOO and LO
would not be overly complicated (bad memory, but maybe it was Tom Davis
referencing the fact that
17 matches
Mail list logo
