From: Larry McVoy <lm@bitmover.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Dan Bethe <dan_bethe@yahoo.com>, linuxppc-dev@lists.linuxppc.org
Subject: Re: the state of the linuxppc-dev community
Date: Tue, 08 Feb 2000 16:46:36 -0800 [thread overview]
Message-ID: <200002090046.QAA04327@work.bitmover.com> (raw)
In-Reply-To: Your message of "Tue, 08 Feb 2000 17:26:05 MST." <Pine.LNX.4.10.10002081724450.30794-100000@opus.bloom.county>
: On Tue, 8 Feb 2000, Tony Mantler wrote:
:
: > Mind you, the PPC-Linux rsync server makes it very easy to get the
: > latest-ish kernel sources, which I used quite successfully recently to
: > compile a kernel for my friend's PBG3. (well, mostly successful. got some
: > missing symbols from some unimportant modules that I didn't care to track
: > down. used the benh sources)
:
: Except that the server is never current, yes. The _only_ place right now
: with any sort of current sources is in bitkeeper trees. So once bk is
: released, things should look a bit better.
In the it-doesn't-help-at-all department, the reason BK hasn't been publicly
released is that we _know_ of bad rename problems. We've been working with
Cort to get those resolved and you'll all be happy to know that the BK
resolve process (the thing that shleps in new work and figures out all the
renames, conflicts, etc) has been rewritten and is passing all regressions.
We're gonna spring it on you by the end of the week. If Cort and the other
BK users bless it, we'll do a public release.
--lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2000-02-09 0:46 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-02-08 23:37 the state of the linuxppc-dev community Dan Bethe
2000-02-09 0:13 ` Tony Mantler
2000-02-09 0:26 ` Tom Rini
2000-02-09 0:46 ` Larry McVoy [this message]
2000-02-09 0:51 ` Tom Rini
2000-02-09 1:02 ` Larry McVoy
-- strict thread matches above, loose matches on Subject: below --
2000-02-09 1:35 Dan Bethe
[not found] <20000209014216.17047.qmail@web1001.mail.yahoo.com>
2000-02-09 9:22 ` Larry McVoy
[not found] <20000208233505.29535.qmail@web1003.mail.yahoo.com>
2000-02-09 0:09 ` Tom Rini
2000-02-09 11:30 ` Michael Schmitz
2000-02-09 17:19 Jan Nieuwenhuizen
[not found] <20000209100229.B5973@linuxcare.com>
2000-02-09 20:04 ` Michael Schmitz
2000-02-09 22:14 ` Tom Rini
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=200002090046.QAA04327@work.bitmover.com \
--to=lm@bitmover.com \
--cc=dan_bethe@yahoo.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).