From: Sebastian Redl <sebastian.redl@getdesigned.at>
To: gentoo-amd64@lists.gentoo.org
Subject: Re: [gentoo-amd64] openoffice 2 compiles?
Date: Tue, 08 Nov 2005 19:15:25 +0100 [thread overview]
Message-ID: <4370EB3D.708@getdesigned.at> (raw)
In-Reply-To: <20051108173035.GA12390@crud.crud.mn.org>
Barry.SCHWARTZ@chemoelectric.org wrote:
>I speak programmer. This is jargon meaning the code is so complicated
>and/or so poorly understood that it might be easier, faster, more
>reliable, better in the long run, and more personally rewarding to
>rewrite. :)
>
>
>
I looked at this presentation. It makes me shudder. I'm aware of the
typical portability problems, but I didn't think OOo was THAT bad.
Sebastian
--
gentoo-amd64@gentoo.org mailing list
next prev parent reply other threads:[~2005-11-08 18:17 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-11-08 6:20 [gentoo-amd64] openoffice 2 compiles? Chris Smart
2005-11-08 12:56 ` Hanno Meyer-Thurow
2005-11-08 16:31 ` Sebastian Redl
2005-11-08 17:23 ` Hanno Meyer-Thurow
2005-11-08 17:30 ` Barry.SCHWARTZ
2005-11-08 18:15 ` Sebastian Redl [this message]
2005-11-08 22:17 ` Chris Smart
-- strict thread matches above, loose matches on Subject: below --
2005-11-08 6:36 Dmitri Pogosyan
2005-11-08 7:16 ` Chris Smart
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4370EB3D.708@getdesigned.at \
--to=sebastian.redl@getdesigned.at \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox