From: Jakub Jelinek <jakub@redhat.com>
To: Jes Sorensen <jes@linuxcare.com>
Cc: Keith Owens <kaos@ocs.com.au>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] modutils 2.3.20 and beyond
Date: Mon, 27 Nov 2000 11:59:42 -0500 [thread overview]
Message-ID: <20001127115942.B1514@devserv.devel.redhat.com> (raw)
In-Reply-To: <1604.975280988@kao2.melbourne.sgi.com> <d3ofz11hur.fsf@lxplus015.cern.ch>
In-Reply-To: <d3ofz11hur.fsf@lxplus015.cern.ch>; from jes@linuxcare.com on Mon, Nov 27, 2000 at 05:48:28PM +0100
On Mon, Nov 27, 2000 at 05:48:28PM +0100, Jes Sorensen wrote:
> >>>>> "Keith" == Keith Owens <kaos@ocs.com.au> writes:
>
> Keith> On Sun, 26 Nov 2000 16:36:55 -0700, "Jeff V. Merkey"
> Keith> <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.
>
> Keith> I have a big problem with Redhat. They make incompatible
> Keith> changes to utilities, do not feed patches back to maintainers
> Keith> then expect the rest of the world to follow their lead. The -i
> Keith> and -m flags to modutils are not the only example, I recently
> Keith> found IA64 and Sparc patches they had added to modutils code
> Keith> and not bothered to tell me. Other distributors are much
> Keith> better about sending me patches, Debian and SuSe in particular
> Keith> do the right thing.
>
> I don't remember where the ia64 modutils patches come from, there were
> some floating around between the ia64 developers for a while. The
> sparc patches I don't have a clue about where come from.
The sparc patches were not sent just because of lack of time on my part,
Jeff Johnson wrote it so that modules compiled with sparc64 gcc 2.96
(basically anything which generates OLO10 relocations) can be inserted and I
wanted to review/test it first myself (and did not get to it early enough).
Jakub
-
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/
prev parent reply other threads:[~2000-11-27 17:30 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
2000-11-27 16:48 ` Jes Sorensen
2000-11-27 16:59 ` Jakub Jelinek [this message]
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=20001127115942.B1514@devserv.devel.redhat.com \
--to=jakub@redhat.com \
--cc=jes@linuxcare.com \
--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