From: Dan Malek <dan@embeddededge.com>
To: acurtis@onz.com
Cc: linuxppc-dev@lists.linuxppc.org
Subject: Re: Cross compile helper patch
Date: Wed, 28 Aug 2002 01:12:09 -0400 [thread overview]
Message-ID: <3D6C5BA9.1060505@embeddededge.com> (raw)
In-Reply-To: NCBBIINEHIPFGJPLBEIFOEEKDLAA.acurtis@onz.com
Allen Curtis wrote:
> .....Only if you are doing cross development do you need to create
> these files. Just a nice logical in the developers face solution to a
> problem that has been solved a 1000 time before.
In 1000 different ways. Like I said, this patch has been submitted by
others in many different forms, and we have politely asked they keep
this local. I don't do my cross compile Makefile changes like you
do, so your changes aren't useful to me, nor to I expect you to want
to this this they way I do.
Thanks.
-- Dan
** Sent via the linuxppc-dev mail list. See http://lists.linuxppc.org/
next prev parent reply other threads:[~2002-08-28 5:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-28 0:02 Cross compile helper patch Allen Curtis
2002-08-28 4:05 ` Dan Malek
2002-08-28 4:22 ` Allen Curtis
2002-08-28 5:12 ` Dan Malek [this message]
2002-08-28 12:01 ` Kenneth Johansson
2002-08-28 14:33 ` Allen Curtis
2002-08-28 15:08 ` Jerry Van Baren
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=3D6C5BA9.1060505@embeddededge.com \
--to=dan@embeddededge.com \
--cc=acurtis@onz.com \
--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.