From: "Yu, Luming" <luming.yu@intel.com>
To: linux-ia64@vger.kernel.org
Subject: RE: Latest 2.4 IA64 Baseline (Bjorn) testing report
Date: Thu, 04 Dec 2003 03:59:26 +0000 [thread overview]
Message-ID: <marc-linux-ia64-107051058731636@msgid-missing> (raw)
In-Reply-To: <marc-linux-ia64-106985955514249@msgid-missing>
Yes, I have done that. And it works now.
Thanks
Luming
-----Original Message-----
From: Bjorn Helgaas [mailto:bjorn.helgaas@hp.com]
Sent: 2003?12?2? 1:42
To: Matthew Wilcox; Yu, Luming
Cc: linux-acpi; linux-ia64@vger.kernel.org
Subject: Re: Latest 2.4 IA64 Baseline (Bjorn) testing report
On Wednesday 26 November 2003 8:14 am, Matthew Wilcox wrote:
> On Wed, Nov 26, 2003 at 11:12:04PM +0800, Yu, Luming wrote:
> > 1. Failed to bk pull http://linux-acpi.bkbits.net/linux-acpi-test-2.4.22 , Error message was
> >
> > " Entire repository is locked by:
> > RESYNC directory.
> > ERROR-Unable to lock repository for update"
>
> This problem's at your end; you need to do some BK magic to fix it.
> I don't use BK myself, but I'm sure somebody else can tell you how to
> fix it.
I think this means a previous "bk pull" is incomplete because it found
changes that need to be merged manually. You should be able to use
"bk resolve" to finish that merge, then retry the new "bk pull".
next prev parent reply other threads:[~2003-12-04 3:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-26 15:12 Latest 2.4 IA64 Baseline (Bjorn) testing report Yu, Luming
2003-11-26 15:14 ` Matthew Wilcox
2003-12-01 17:42 ` Bjorn Helgaas
2003-12-03 12:44 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Lion) Yu, Luming
2003-12-03 14:25 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Tiger) Yu, Luming
2003-12-04 3:59 ` Yu, Luming [this message]
2003-12-10 9:41 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Lion) Yu, Luming
2003-12-10 9:46 ` Yu, Luming
2003-12-10 10:00 ` Latest 2.4 IA64 Baseline (Bjorn) testing report (Tiger) Yu, Luming
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=marc-linux-ia64-107051058731636@msgid-missing \
--to=luming.yu@intel.com \
--cc=linux-ia64@vger.kernel.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