From: Dave Nellans <dnellans@cs.utah.edu>
To: Brandon Low <lostlogic@gentoo.org>
Cc: gentoo-dev@gentoo.org
Subject: Re: [gentoo-dev] db-3.2.9-r2
Date: 24 Feb 2003 14:39:01 -0700 [thread overview]
Message-ID: <1046122741.4339.10.camel@malfus> (raw)
In-Reply-To: <20030224210337.GA32763@lostlogicx.com>
[-- Attachment #1: Type: text/plain, Size: 280 bytes --]
Worked ok here on several x86 boxes... what breaks?
dave
On Mon, 2003-02-24 at 14:03, Brandon Low wrote:
> This new revision won't build for me, has anyone else had troubles or is it just me? Thanks!
>
> --Brandon
>
> --
> gentoo-dev@gentoo.org mailing list
--
[-- Attachment #2: This is a digitally signed message part --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
next prev parent reply other threads:[~2003-02-24 21:54 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-24 21:03 [gentoo-dev] db-3.2.9-r2 Brandon Low
2003-02-24 21:39 ` Dave Nellans [this message]
2003-02-24 22:39 ` Brandon Low
2003-02-24 23:38 ` Matt Tucker
2003-02-24 23:44 ` Matt Tucker
2003-02-25 1:15 ` Brandon Low
2003-02-24 21:39 ` Henti Smith
2003-02-24 21:39 ` Jay Pfeifer
2003-02-24 22:25 ` Peter Ruskin
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=1046122741.4339.10.camel@malfus \
--to=dnellans@cs.utah.edu \
--cc=gentoo-dev@gentoo.org \
--cc=lostlogic@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