From: Larry McVoy <lm@bitmover.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Iain Sandoe <iain@sandoe.co.uk>, linuxppc-dev@lists.linuxppc.org
Subject: Re: which bk version to use (was re: 2.4.0 & ac1)
Date: Mon, 8 Jan 2001 09:12:55 -0800 [thread overview]
Message-ID: <20010108091255.A3077@work.bitmover.com> (raw)
In-Reply-To: <20010108100432.L19404@opus.bloom.county>
On Mon, Jan 08, 2001 at 10:04:32AM -0700, Tom Rini wrote:
>
> On Mon, Jan 08, 2001 at 05:00:36PM +0000, Iain Sandoe wrote:
> >
> > On Mon, Jan 8, 2001, Tom Rini wrote:
> >
> > [...]
> >
> > >> so what's on the rsync linuxppc_2_3 ?
> > >
> > > No idea. It might be 2_4 it might not be. :)
> >
> > can you post something when it is known?
> > (I find rsync very useful).
>
> I'll ask.
>
> > > The 2_4 tree is building. If it's not building, report it here.
> >
> > OK... supposing I get bk... which version of BK do I need?...
> >
> > I ask because I read a comment on bk-user that the latest version may not be
> > right for the PPC trees... is that an up-to-date statement?
>
> Unfortunatly, probably. The "stable" bk (ie 1.2) is what you want.
Yup. You don't want to switch to the 2.0beta stuff yet, we need to redo the
triggers one more time.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2001-01-08 17:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-01-08 17:00 which bk version to use (was re: 2.4.0 & ac1) Iain Sandoe
2001-01-08 17:04 ` Tom Rini
2001-01-08 17:12 ` Larry McVoy [this message]
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=20010108091255.A3077@work.bitmover.com \
--to=lm@bitmover.com \
--cc=iain@sandoe.co.uk \
--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).