From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: diekema_jon <diekema@bucks.si.com>, linuxppc-embedded@lists.linuxppc.org
Subject: Re: Root keys on bk://bitkeeper.fsmlabs.com:5000 have changed
Date: Sat, 06 Jan 2001 20:39:59 +0100 [thread overview]
Message-ID: <200101061940.f06Jdx904796@denx.local.net> (raw)
In-Reply-To: Your message of "Sat, 06 Jan 2001 10:47:11 MST." <20010106104711.D1400@opus.bloom.county>
In message <20010106104711.D1400@opus.bloom.county> you wrote:
>
> > It appears that the BitKeeper repository at bk://bitkeeper.fsmlabs.com:5000
> > has changed. What happened to the previous BK tree? Was it replaced with the
> > 2.4.0 baseline?
>
> The former 2_3 tree has been replaced with a new 2_4 tree which currently does
> _not_ have all of the fixes needed for PPC.
Is there some place where such decisions are discussed or at least
announced?
Things like that hit my with surprise again and again (and obviously
not only me).
A few days ago Steven Hanley <sjh@wibble.net> asked for the currently
active devel tree. The question has not been answered yet.
I really would appreciate a summary about the current state of the
different source trees.
Any comment from the Powers That Be?
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
Any time things appear to be going better, you have overlooked some-
thing.
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-06 19:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-06 16:50 Root keys on bk://bitkeeper.fsmlabs.com:5000 have changed diekema_jon
2001-01-06 17:47 ` Tom Rini
2001-01-06 19:39 ` Wolfgang Denk [this message]
2001-01-06 20:11 ` Tom Rini
[not found] ` <20010107031448.H13210@hq.fsmlabs.com>
[not found] ` <3A58CCC6.75B79975@mvista.com>
2001-01-08 21:22 ` Cort Dougan
2001-01-07 10:13 ` Cort Dougan
2001-01-08 10:03 ` Gabriel Paubert
2001-01-08 21:21 ` Cort Dougan
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=200101061940.f06Jdx904796@denx.local.net \
--to=wd@denx.de \
--cc=diekema@bucks.si.com \
--cc=linuxppc-embedded@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.