From: Pete Zaitcev <zaitcev@redhat.com>
To: Konrad Eisele <eiselekd@web.de>
Cc: PeteZaitcev <zaitcev@redhat.com>, linux-kernel@vger.kernel.org
Subject: perl (Was: Adding sparc-leon linux to sourcetree)
Date: Thu, 30 Jan 2003 13:55:28 -0500 [thread overview]
Message-ID: <20030130135528.C12226@devserv.devel.redhat.com> (raw)
In-Reply-To: <200301301353.h0UDrxO24129@mailgate5.cinetic.de>; from eiselekd@web.de on Thu, Jan 30, 2003 at 02:53:59PM +0100
> Date: Thu, 30 Jan 2003 14:53:59 +0100
> From: Konrad Eisele <eiselekd@web.de>
> There is also one change I have made on the buildsystem. Because
> I'm using some perl inline scripts in the $cmd_xxx the >'< and >$<
> signs in the inline perl scripts cause trouble (perl -e '...$x=....'),
> the >'< because of the echo command, the >$< when rereading from
> the xxx..cmd files. Could this be applied to the original file?
First, send a patch, not a chunk of a Makefile.
Second, this is something I defer to Kai, Sam, & Co.
Personally, I am opposed to a use of perl, because it's not
installed in my sparc userland, so I would not be able to
self-compile a leon or joint kernel. But ultimately this is
not my call to decide. At one point, Linus approved Python
into the toolchain. So, present good evidence of need and post
to lists.
-- Pete
prev parent reply other threads:[~2003-01-30 18:46 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200301301353.h0UDrxO24129@mailgate5.cinetic.de>
2003-01-30 18:44 ` Adding sparc-leon linux to sourcetree Pete Zaitcev
2003-01-30 18:55 ` Pete Zaitcev [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=20030130135528.C12226@devserv.devel.redhat.com \
--to=zaitcev@redhat.com \
--cc=eiselekd@web.de \
--cc=linux-kernel@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