From: Tom Rini <trini@kernel.crashing.org>
To: Wolfgang Denk <wd@denx.de>
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, 6 Jan 2001 13:11:55 -0700 [thread overview]
Message-ID: <20010106131155.E556@opus.bloom.county> (raw)
In-Reply-To: <200101061940.f06Jdx904796@denx.local.net>; from wd@denx.de on Sat, Jan 06, 2001 at 08:39:59PM +0100
On Sat, Jan 06, 2001 at 08:39:59PM +0100, Wolfgang Denk wrote:
> 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?
Formally? Nope. You just got the announcement. :)
> Things like that hit my with surprise again and again (and obviously
> not only me).
Hey, it supprised me this morning to find out it had changed. But it was also
expected. 2.3 is dead, it's now 2.4.
> A few days ago Steven Hanley <sjh@wibble.net> asked for the currently
> active devel tree. The question has not been answered yet.
Active devel for what? The 2_5 tree (I'm sure if you search the -dev archives
there's a few pointers to it, bk://bk.fsmlabs.com:5005 is where the unstable
stuff happens, before moving to a stable tree.
> I really would appreciate a summary about the current state of the
> different source trees.
Sure:
linuxppc_2_3 - "Dead", it still exists on the server, but it's going away.
linuxppc_2_4 - Where 2_3 used to be. It doesn't compile at the moment, but it
will later today / tomorrow (I'm testing it right now).
linuxppc_2_5 - Same old unstable dev tree, still port 5005
> Any comment from the Powers That Be?
I don't know if I count, I just commit stuff :)
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2001-01-06 20:11 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
2001-01-06 20:11 ` Tom Rini [this message]
[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=20010106131155.E556@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=diekema@bucks.si.com \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=wd@denx.de \
/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