From: Tom Rini <trini@kernel.crashing.org>
To: Gavin Hemphill <hemphill@drea.dnd.ca>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: bk trees broken?
Date: Fri, 29 Mar 2002 09:13:40 -0700 [thread overview]
Message-ID: <20020329161340.GA735@opus.bloom.county> (raw)
In-Reply-To: <3CA48DEE.78A803@drea.dnd.ca>
On Fri, Mar 29, 2002 at 11:53:18AM -0400, Gavin Hemphill wrote:
> Are there problems with the bk trees for linuxppc_2_4 and linuxppc-2.5.
> I've been getting error messages "ERROR-Lock fail: possible permission
> problem." on them for the last few days. I've made sure I'm running the
> latest bk (BitKeeper/Free version is bk-2.1.6-pre3 20020328212052 for
> powerpc-glibc21-linux) and even tried re-cloning the repositories. The
> linuxppc_2_4_devel tree seems to work fine.
BitMover lost a disk a few days ago. If this is still a problem, please
email support@bitmover.com, or use the BK mirrors on source.mvista.com.
--
Tom Rini (TR1265)
http://gate.crashing.org/~trini/
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
prev parent reply other threads:[~2002-03-29 16:13 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-03-29 15:53 bk trees broken? Gavin Hemphill
2002-03-29 15:59 ` Geert Uytterhoeven
2002-03-29 16:13 ` Tom Rini [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=20020329161340.GA735@opus.bloom.county \
--to=trini@kernel.crashing.org \
--cc=hemphill@drea.dnd.ca \
--cc=linuxppc-dev@lists.linuxppc.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