Re: the state of the linuxppc-dev community

2 messages, 2 authors, 2000-02-09 · open the first message on its own page

Re: the state of the linuxppc-dev community

From: Larry McVoy <hidden>
Date: 2000-02-09 00:46:36

: 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/

Re: the state of the linuxppc-dev community

From: Tom Rini <hidden>
Date: 2000-02-09 00:51:14

On Tue, 8 Feb 2000, Larry McVoy wrote:
: 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.
ooh ooh ooh, you mean it might finally be out?  It has _not_ helped any
that the only up to date trees have been hidden from the public.
Duplication of work, general annoyance, etc.

---
Tom Rini (TR1265)
http://gate.crashing.org/~trini/


** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help