From: "Bo Ørsted Andresen" <bo.andresen@zlin.dk>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] eselect could not source blas.eselect
Date: Thu, 12 Oct 2006 20:40:04 +0200 [thread overview]
Message-ID: <200610122040.09894.bo.andresen@zlin.dk> (raw)
In-Reply-To: <9b1675090610120951w76e2b392l5342865d691447d7@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 351 bytes --]
On Thursday 12 October 2006 18:51, Trenton Adams wrote:
> Ahah, looks like you just found a bug Bo.
[SNIP]
To be honest I don't have a clue about what I just found. I am not seeing this
behaviour on any of my systems. But I guess it is time to go file a bug and
include that info (and the info from the original post)...
--
Bo Andresen
[-- Attachment #2: Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2006-10-12 19:03 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-12 2:56 [gentoo-user] eselect could not source blas.eselect Trenton Adams
2006-10-12 4:30 ` Bo Ørsted Andresen
2006-10-12 4:41 ` Trenton Adams
2006-10-12 5:30 ` Bo Ørsted Andresen
2006-10-12 14:47 ` Trenton Adams
2006-10-12 16:14 ` Bo Ørsted Andresen
2006-10-12 16:51 ` Trenton Adams
2006-10-12 18:40 ` Bo Ørsted Andresen [this message]
2006-10-12 19:06 ` Trenton Adams
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=200610122040.09894.bo.andresen@zlin.dk \
--to=bo.andresen@zlin.dk \
--cc=gentoo-user@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