From: "Jeff V. Merkey" <jmerkey@vger.timpanogas.org>
To: Keith Owens <kaos@ocs.com.au>
Cc: linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modutils 2.3.20 and beyond
Date: Sun, 26 Nov 2000 19:43:14 -0700 [thread overview]
Message-ID: <20001126194314.B2265@vger.timpanogas.org> (raw)
In-Reply-To: <20001126163655.A1637@vger.timpanogas.org> <1604.975280988@kao2.melbourne.sgi.com>
In-Reply-To: <1604.975280988@kao2.melbourne.sgi.com>; from kaos@ocs.com.au on Mon, Nov 27, 2000 at 10:23:08AM +1100
On Mon, Nov 27, 2000 at 10:23:08AM +1100, Keith Owens wrote:
> On Sun, 26 Nov 2000 16:36:55 -0700,
> "Jeff V. Merkey" <jmerkey@vger.timpanogas.org> wrote:
> >Keith,
> >
> >Please consider the attached patch for inclusion in all future versions
> >of the modutils depmod program for compatiblity with RedHat and
> >RedHat derived Linux distributions.
>
> I have a big problem with Redhat. They make incompatible changes to
> utilities, do not feed patches back to maintainers then expect the rest
> of the world to follow their lead. The -i and -m flags to modutils are
> not the only example, I recently found IA64 and Sparc patches they had
> added to modutils code and not bothered to tell me. Other distributors
> are much better about sending me patches, Debian and SuSe in particular
> do the right thing.
>
> Since "-F System.map" in modutils is equivalent to "-m System.map -i"
> and works on all distributions, not just Redhat, the "-m -i" patch is
> unnecessary. Consider this my protest against bad habits by
> distributors, they created the mess with their lack of communication
> and they have to fix it.
Well Keith, I will never fail to post back changes to you, as evidenced
by the fact I did send you one. Anconda is open sourced, and as such,
is no longer owned by any distributor. The question is whether to
diverge it from theirs. I would like to not do this, since, as you
point out, it generates changes back the other way.
It's your call. I can keep the patch around because I really don't
want to diverge anaconda any more than I have to. At some point,
perhaps they will get changes to you more timely.
:-)
Jeff
-
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-27 2:17 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
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 [this message]
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=20001126194314.B2265@vger.timpanogas.org \
--to=jmerkey@vger.timpanogas.org \
--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