mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Tom Rini <trini@kernel.crashing.org>
Cc: "Mohammad A. Haque" <mhaque@haque.net>,
	Alan Cox <alan@lxorguk.ukuu.org.uk>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modutils 2.3.20 and beyond
Date: Sun, 26 Nov 2000 19:39:28 -0700	[thread overview]
Message-ID: <20001126193928.A2265@vger.timpanogas.org> (raw)
In-Reply-To: <20001126163655.A1637@vger.timpanogas.org> <E140AZB-0002Qh-00@the-village.bc.nu> <20001126164556.B1665@vger.timpanogas.org> <3A21968B.5CDB12BF@haque.net> <20001126170334.B1787@vger.timpanogas.org> <20001126161502.E872@opus.bloom.county>
In-Reply-To: <20001126161502.E872@opus.bloom.county>; from trini@kernel.crashing.org on Sun, Nov 26, 2000 at 04:15:02PM -0700

On Sun, Nov 26, 2000 at 04:15:02PM -0700, Tom Rini wrote:
> On Sun, Nov 26, 2000 at 05:03:34PM -0700, Jeff V. Merkey wrote:
> 
> > Great.  Then tell RedHat to rewrite it without the need for these switches.
> > They will say NO.  It's a trivial change, and would save me a lot of hours
> > rewriting scripts.  I did it once, but if RedHat has standardized on this
> > set of switches, why not add them as alias commands?  It's a trivial 
> > patch.
> 
> I hate to jump in here in the middle of a perfectly good argument but I'd like
> to point out a few things:
> a) If RedHat/RedHat-like distros needs these changes they can include this
> patch.  The plus side is it won't piss off the people that seem to care and
> don't use said distros the down side is that if/when another security update
> comes out people will have to hope this patch applies easily still, if they
> update themselves.
> b) Are these switches which used to be valid in modutils 2.3.x?  If so, why?
> It makes perfect sense to keep this patch around until modutils 2.4 (or 2.5
> if modutils version is still supposed to match kernel version).  If these
> are old modutils 2.2.x switches, see part a).
> And c) Why does it matter if RedHat/etc would have to adapt their scripts.
> There's always part a, or what debian does for stable sometimes, backporting
> fixes.  Or even lots of sed & awk magic.

Oh well.  Look like %patch -p1 in the rpm for now.

Jeff

> 
> -- 
> Tom Rini (TR1265)
> http://gate.crashing.org/~trini/
-
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/

  reply	other threads:[~2000-11-27  2:13 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2000-11-26 23:36 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 [this message]
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
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=20001126193928.A2265@vger.timpanogas.org \
    --to=jmerkey@vger.timpanogas.org \
    --cc=alan@lxorguk.ukuu.org.uk \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mhaque@haque.net \
    --cc=trini@kernel.crashing.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

all inboxes | Powered by JetHome®