From: Larry McVoy <lm@bitmover.com>
To: "David M?ller (ELSOFT AG)" <d.mueller@elsoft.ch>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Problem with bk repository?
Date: Wed, 7 Aug 2002 08:12:35 -0700 [thread overview]
Message-ID: <20020807081235.A25094@work.bitmover.com> (raw)
In-Reply-To: <3D4FEA26.1070403@elsoft.ch>; from d.mueller@elsoft.ch on Tue, Aug 06, 2002 at 05:24:22PM +0200
There was a corrupted PPC logging tree and I have fixed that. I apologize
for any problems, we are working on trying to make this stuff work better.
On Tue, Aug 06, 2002 at 05:24:22PM +0200, "David M?ller (ELSOFT AG)" wrote:
>
> Hello
>
> In the last few days and weeks, i'm seeing in increasing number of
> errors like this:
>
> david@devil:/repository/linuxppc_2_4_devel>bk parent
> Parent repository is bk://ppc.bkbits.net/linuxppc_2_4_devel
> david@devil:/repository/linuxppc_2_4_devel>bk pull -ll
> ERROR-Can't get read lock on the repository.
> pull: remote locked, trying again...
> ERROR-Can't get read lock on the repository.
> pull: remote locked, trying again...
> ERROR-Can't get read lock on the repository.
> pull: remote locked, trying again...
> ERROR-Can't get read lock on the repository.
> pull: remote locked, trying again...
>
>
> Is this something to worry about or just some kind of "bandwidth
> limitation"?
>
>
> Dave
>
>
--
---
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:[~2002-08-07 15:12 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 15:24 Problem with bk repository? "David Müller (ELSOFT AG)"
2002-08-06 15:46 ` acurtis
2002-08-06 16:13 ` Tom Rini
2002-08-07 0:12 ` David Gibson
2002-08-07 0:29 ` Larry McVoy
2002-08-07 15: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=20020807081235.A25094@work.bitmover.com \
--to=lm@bitmover.com \
--cc=d.mueller@elsoft.ch \
--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 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.