From: Gary Thomas <gary@mlbassoc.com>
To: Tom Rini <trini@kernel.crashing.org>
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: BK problems with linuxppc-2.5
Date: 11 Aug 2003 11:17:33 -0600 [thread overview]
Message-ID: <1060622253.31273.271.camel@hermes> (raw)
In-Reply-To: <20030811171247.GC807@ip68-0-152-218.tc.ph.cox.net>
On Mon, 2003-08-11 at 11:12, Tom Rini wrote:
> On Sat, Aug 09, 2003 at 07:38:43AM -0600, Gary Thomas wrote:
>
> >
> > I've been unable to access this repository [for days].
> >
> > [gthomas@hermes tmp]$ bk clone bk://source.mvista.com/linuxppc-2.5 linuxppc-2.5
> > ERROR-Can't get read lock on the repository.
> >
> > Any ideas/help?
>
> This should be fixed now.
Yes, thanks. Any feedback what was stuck? (I tried it just a few
hours ago and it was still broken, so you obviously did something)
--
Gary Thomas <gary@mlbassoc.com>
MLB Associates
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2003-08-11 17:17 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E19lS18-0003Ng-00@source.mvista.com>
2003-08-09 13:38 ` BK problems with linuxppc-2.5 Gary Thomas
2003-08-11 17:12 ` Tom Rini
2003-08-11 17:17 ` Gary Thomas [this message]
2003-08-11 17:31 ` Tom Rini
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=1060622253.31273.271.camel@hermes \
--to=gary@mlbassoc.com \
--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).