From: "Allen Curtis" <acurtis@onz.com>
To: "Momchil Velikov" <velco@fadata.bg>
Cc: <linuxppc-dev@lists.linuxppc.org>
Subject: RE: BK... a little help please
Date: Tue, 28 May 2002 06:39:40 -0700 [thread overview]
Message-ID: <NCBBIINEHIPFGJPLBEIFAELEDHAA.acurtis@onz.com> (raw)
In-Reply-To: <87elfwahls.fsf@fadata.bg>
> Allen> Check FAILED, contact BitMover.
>
> Well, contact BitMover.
I thought that since BK is complaining about something that happened when
building from the PPC source tree that either:
a) Someone had seen this before and knew the solution
b) Perhaps it is something that needs to be addressed in the build process
so BK does not complain about things that you did not modify and therefore
do not need to be checked out for edit or submitted back to the source tree
at a future date.
Perhaps I was wrong....
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-05-28 13:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-05-28 3:34 BK... a little help please Allen Curtis
2002-05-28 6:53 ` Momchil Velikov
2002-05-28 13:39 ` Allen Curtis [this message]
2002-05-28 21:56 ` Val Henson
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=NCBBIINEHIPFGJPLBEIFAELEDHAA.acurtis@onz.com \
--to=acurtis@onz.com \
--cc=linuxppc-dev@lists.linuxppc.org \
--cc=velco@fadata.bg \
/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).