From: "Bryan O'Sullivan" <bos@serpentine.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Hugo Mills <hugo-lkml@carfax.org.uk>,
Vojtech Pavlik <vojtech@suse.cz>,
bitkeeper-announce@work.bitmover.com,
linux-kernel@vger.kernel.org
Subject: Re: bk-3.2.0 released
Date: Sat, 29 May 2004 13:13:35 -0700 [thread overview]
Message-ID: <1085861614.2620.11.camel@camp4.serpentine.com> (raw)
In-Reply-To: <20040529154714.GC20605@work.bitmover.com>
On Sat, 2004-05-29 at 08:47, Larry McVoy wrote:
> So is Fedora 1 OK with you? Any
> nay sayers?
Fedora Core 1 and SuSE 9.0 use roughly the same version of glibc (2.3.2,
with some divergent patches), and the two seem fairly compatible in that
regard based on a little testing I just did.
If you use any libstdc++ stuff, you'll want to build on SuSE 9.0, which
has an older libstdc++.
<b
next prev parent reply other threads:[~2004-05-29 20:13 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-05-18 23:32 Larry McVoy
2004-05-19 6:51 ` Christoph Hellwig
2004-05-19 14:02 ` Larry McVoy
2004-05-19 14:11 ` Jan-Benedict Glaw
2004-05-19 14:16 ` Larry McVoy
2004-05-19 14:23 ` Kevin P. Fleming
2004-05-19 14:36 ` John Bradford
2004-05-19 18:47 ` Tomas Szepe
2004-05-19 14:26 ` Jan-Benedict Glaw
2004-05-19 14:48 ` Larry McVoy
2004-05-19 15:00 ` Jan-Benedict Glaw
2004-05-19 15:09 ` Larry McVoy
2004-05-19 16:10 ` Nicolas Pitre
2004-05-19 20:06 ` Valdis.Kletnieks
2004-05-19 21:20 ` Stan Bubrouski
2004-05-19 14:33 ` Christoph Hellwig
2004-05-19 14:32 ` Christoph Hellwig
2004-05-19 14:34 ` John Bradford
2004-05-19 15:41 ` Bill Davidsen
2004-05-20 3:10 ` Jeff Sipek
2004-05-29 9:54 ` Vojtech Pavlik
2004-05-29 13:04 ` Larry McVoy
2004-05-29 13:15 ` Hugo Mills
2004-05-29 13:20 ` Larry McVoy
2004-05-29 15:47 ` Larry McVoy
2004-05-29 20:13 ` Bryan O'Sullivan [this message]
2004-05-30 3:59 ` David Lang
2004-05-29 13:20 ` Vojtech Pavlik
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=1085861614.2620.11.camel@camp4.serpentine.com \
--to=bos@serpentine.com \
--cc=bitkeeper-announce@work.bitmover.com \
--cc=hugo-lkml@carfax.org.uk \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=vojtech@suse.cz \
/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
all inboxes | Powered by JetHome®