From: "J . A . Magallon" <jamagallon@able.es>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: LKCD from SGI
Date: Sat, 25 Nov 2000 14:49:04 +0100 [thread overview]
Message-ID: <20001125144904.E2877@werewolf.able.es> (raw)
In-Reply-To: <20001125141830.C2877@werewolf.able.es> <7235.975158637@ocs3.ocs-net>
In-Reply-To: <7235.975158637@ocs3.ocs-net>; from kaos@ocs.com.au on Sat, Nov 25, 2000 at 14:23:57 +0100
On Sat, 25 Nov 2000 14:23:57 Keith Owens wrote:
> On Sat, 25 Nov 2000 14:18:30 +0100,
> "J . A . Magallon" <jamagallon@able.es> wrote:
> >Could the default target install names int the std kernel be changed to
> >System.map -> System.map-$(KERNELRELEASE)
> >vmlinuz -> vmlinuz-$(KERNELRELEASE)
> >and then symlink to that ?
>
> We could do a lot of things in the install targets. But none of them
> are going to be done before kernel 2.5. We are in code freeze (is this
> freeze number 4 or 5?). Changing the install method just before a new
> kernel branch is released will not be popular with the distributors.
Yes, I know. I thought you were talking about '2.5 kernel build wish list'.
--
Juan Antonio Magallon Lacarta #> cd /pub
mailto:jamagallon@able.es #> more beer
Linux 2.2.18-pre23-vm #3 SMP Wed Nov 22 22:33:53 CET 2000 i686 unknown
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-11-25 14:19 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-22 15:20 LKCD from SGI 64738
2000-11-22 18:14 ` Matt D. Robinson
2000-11-23 1:41 ` Peter Samuelson
2000-11-24 23:40 ` Eric W. Biederman
2000-11-25 1:58 ` Keith Owens
2000-11-25 13:18 ` J . A . Magallon
2000-11-25 13:23 ` Keith Owens
2000-11-25 13:49 ` J . A . Magallon [this message]
2000-11-25 13:44 ` Matthew Kirkwood
-- strict thread matches above, loose matches on Subject: below --
2000-11-25 15:17 64738
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=20001125144904.E2877@werewolf.able.es \
--to=jamagallon@able.es \
--cc=kaos@ocs.com.au \
--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