From: David Ford <david@linux.com>
To: LKML <linux-kernel@vger.kernel.org>,
"Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
Subject: Re: [PATCH] modutils 2.3.20 and beyond
Date: Sun, 26 Nov 2000 16:13:20 -0800 [thread overview]
Message-ID: <3A21A720.75A4EEB1@linux.com> (raw)
In-Reply-To: <20001126163655.A1637@vger.timpanogas.org> <E140AZB-0002Qh-00@the-village.bc.nu> <20001126164556.B1665@vger.timpanogas.org>
[-- Attachment #1: Type: text/plain, Size: 619 bytes --]
"Jeff V. Merkey" wrote:
> On Sun, Nov 26, 2000 at 10:46:35PM +0000, Alan Cox wrote:
> > > + {"ignore-versions", 0, 0, 'i'},
> >
> > I dont think we should encourage anyone to ignore symbol versions
>
> Anaconda will barf and require over 850+ changes to the scripts without
> it. If you look at the patch, you will note that it's a silent switch
> that's only there to avoid a noisy error message from depmod. It
> actually does nothing other than set a flag that also does nothing.
> -m simply maps to -F.
It's still a bad precedent. Anaconda should have been written correctly in
the first place.
-d
[-- Attachment #2: Card for David Ford --]
[-- Type: text/x-vcard, Size: 176 bytes --]
begin:vcard
n:Ford;David
x-mozilla-html:TRUE
adr:;;;;;;
version:2.1
email;internet:david@kalifornia.com
title:Blue Labs Developer
x-mozilla-cpt:;14688
fn:David Ford
end:vcard
next prev parent reply other threads:[~2000-11-27 0:43 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-11-26 23:36 [PATCH] modutils 2.3.20 and beyond Jeff V. Merkey
2000-11-26 22:46 ` Alan Cox
2000-11-26 23:27 ` H. Peter Anvin
2000-11-26 23:45 ` Jeff V. Merkey
2000-11-26 23:02 ` Mohammad A. Haque
2000-11-27 0:03 ` Jeff V. Merkey
2000-11-26 23:15 ` Tom Rini
2000-11-27 2:39 ` Jeff V. Merkey
2000-11-27 0:16 ` David Ford
2000-11-27 2:46 ` Jeff V. Merkey
2000-11-27 1:58 ` Tom Rini
2000-11-27 0:13 ` David Ford [this message]
2000-11-27 2:11 ` Alan Cox
2000-11-27 3:33 ` Jeff V. Merkey
2000-11-26 23:23 ` Keith Owens
2000-11-27 2:43 ` Jeff V. Merkey
2000-11-27 16:48 ` Jes Sorensen
2000-11-27 16:59 ` Jakub Jelinek
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=3A21A720.75A4EEB1@linux.com \
--to=david@linux.com \
--cc=jmerkey@vger.timpanogas.org \
--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