All of lore.kernel.org
 help / color / mirror / Atom feed
From: Johannes Erdfelt <johannes@erdfelt.com>
To: linux-hotplug@vger.kernel.org
Subject: Re: modutils 2.4.2, please test asap
Date: Mon, 22 Jan 2001 20:16:42 +0000	[thread overview]
Message-ID: <marc-linux-hotplug-98019805609367@msgid-missing> (raw)
In-Reply-To: <marc-linux-hotplug-98018911111962@msgid-missing>

On Tue, Jan 23, 2001, Keith Owens <kaos@ocs.com.au> wrote:
> On Mon, 22 Jan 2001 11:37:47 -0800, 
> Miles Lane <miles@megapathdsl.net> wrote:
> >Hey.  Let's be fair here.  Linus rejected your patch for reasons that
> >had absolutely nothing to do with USB backport support issues.
> 
> On the contrary.  Linus rejected the patch because
> 
>   "I'd much rather just have the 2.4.0 behaviour, and no versioning.
>   Tell people that 2.4.0-test kernels won't work. They'll notice on
>   their own."
> 
> and
> 
>   "The fact that such modutils binaries won't work with pre-2.4.0
>   kernels is not even on my radar screen, quite frankly.  There isn't
>   even an installed base of people using it, and I don't think anybody
>   of the developers using it are still using pre-kernels. In short, I
>   see absolutely no reason for even trying to maintain any backwards
>   compatibility in this area.".
> 
> Because the USB maintainers did not want to support backwards
> compatibility, Linus saw no need for the patch.  Which is fine, if you
> are happy to break backwards compatibility.  It should be obvious that
> I disagree strongly with this attitude.

Just to clarify, I see no reason for supporting backwards compatibility
with development kernels. I completely agree with Linus wrt to this
decision.

As for 2.2 kernels, that's a different matter. It's essentially a fork
the 2.4 code which has been tracking changes and backporting them as
necessary.

Hotplugging is another whole ball of wax in 2.2.

JE


_______________________________________________
Linux-hotplug-devel mailing list  http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
http://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel

  parent reply	other threads:[~2001-01-22 20:16 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-01-22 18:24 modutils 2.4.2, please test asap Keith Owens
2001-01-22 19:28 ` Keith Owens
2001-01-22 19:37 ` Miles Lane
2001-01-22 19:58 ` Stephen J. Gowdy
2001-01-22 20:05 ` Miles Lane
2001-01-22 20:16 ` Johannes Erdfelt [this message]
2001-01-22 20:30 ` David Brownell
2001-01-22 21:40 ` Keith Owens
2001-01-22 22:29 ` Johannes Erdfelt
2001-01-22 22:51 ` Keith Owens
2001-01-22 23:09 ` Greg KH
2001-01-22 23:21 ` David Brownell
2001-01-22 23:38 ` Miles Lane
2001-01-22 23:42 ` Keith Owens
2001-01-23  2:52 ` David Brownell
2001-01-23  3:25 ` Keith Owens

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=marc-linux-hotplug-98019805609367@msgid-missing \
    --to=johannes@erdfelt.com \
    --cc=linux-hotplug@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.