From: Richard Henderson <rth@twiddle.net>
To: Keith Owens <kaos@ocs.com.au>, Pavel Machek <pavel@suse.cz>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: [patch] kernel/module.c (plus gratuitous rant)
Date: Sat, 28 Oct 2000 17:27:00 -0700 [thread overview]
Message-ID: <20001028172700.A13608@twiddle.net> (raw)
In-Reply-To: <20001027194513.A1060@bug.ucw.cz> <4309.972694843@ocs3.ocs-net> <20001028131558.A17429@uni-mainz.de>
In-Reply-To: <20001028131558.A17429@uni-mainz.de>
On Sat, Oct 28, 2000 at 01:15:58PM +0200, Dominik Kubla wrote:
> Even simpler: "gcc -V 2.7.2.3" or "gcc -V 2.95.2" or whatever...
Which was a nice idea, but it doesn't actually work. Changes
in spec file format between versions makes this fall over.
r~
-
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-10-29 0:28 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <39F5830E.7963A935@uow.edu.au>
[not found] ` <Pine.LNX.4.10.10010241353590.1743-100000@penguin.transmeta.com>
2000-10-27 17:45 ` [patch] kernel/module.c (plus gratuitous rant) Pavel Machek
2000-10-27 20:40 ` Jeff Garzik
2000-10-27 21:12 ` Alan Cox
2000-10-27 20:46 ` Alan Cox
2000-10-28 1:00 ` Keith Owens
2000-10-28 11:15 ` Dominik Kubla
2000-10-29 0:27 ` Richard Henderson [this message]
2000-10-29 15:09 ` Dominik Kubla
2000-10-30 11:05 ` Peter Samuelson
2000-10-30 18:50 ` Richard Henderson
2000-10-29 23:23 ` Rusty Russell
2000-10-30 11:08 ` Peter Samuelson
2000-10-30 11:19 ` Recommended compiler? - " Linux Kernel Developer
2000-10-30 11:58 ` Peter Samuelson
2000-10-30 13:49 ` Martin Dalecki
2000-10-30 20:50 ` Horst von Brand
2000-10-30 22:02 ` Jakub Jelinek
2000-10-31 10:27 ` Martin Dalecki
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=20001028172700.A13608@twiddle.net \
--to=rth@twiddle.net \
--cc=kaos@ocs.com.au \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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