From: Anton Starikov <antst@ifm.liu.se>
To: Donnie Berkholz <spyderous@gentoo.org>
Cc: gentoo-dev@lists.gentoo.org
Subject: Re: [gentoo-dev] ifc USE flag, fortran support and some general notes about multi-compiler support
Date: Thu, 26 Aug 2004 02:47:08 +0200 [thread overview]
Message-ID: <412D330C.2020806@ifm.liu.se> (raw)
In-Reply-To: <1093474769.31933.2.camel@localhost>
Donnie Berkholz wrote:
> You seem to be rejecting it out of hand
> rather than considering an expansion of its functionality.
Sorry, that was my fault. Just misunderstanding.
Anton.
--
gentoo-dev@gentoo.org mailing list
next prev parent reply other threads:[~2004-08-26 0:47 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-25 20:06 [gentoo-dev] ifc USE flag, fortran support and some general notes about multi-compiler support Anton Starikov
2004-08-25 20:25 ` Donnie Berkholz
2004-08-25 20:28 ` Donnie Berkholz
2004-08-25 21:26 ` Anton Starikov
2004-08-25 22:59 ` Donnie Berkholz
2004-08-26 0:31 ` Anton Starikov
2004-08-26 0:47 ` Anton Starikov [this message]
2004-08-25 21:12 ` Anton Starikov
2004-08-25 23:46 ` Olivier Fisette
2004-08-26 0:37 ` Anton Starikov
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=412D330C.2020806@ifm.liu.se \
--to=antst@ifm.liu.se \
--cc=gentoo-dev@lists.gentoo.org \
--cc=spyderous@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