From: "David S. Miller" <davem@redhat.com>
To: marcelo@conectiva.com.br
Cc: ledzep37@attbi.com, linux-kernel@vger.kernel.org
Subject: Re: __devexit_p() in linux-2.5.1-preX?
Date: Thu, 13 Dec 2001 12:21:26 -0800 (PST) [thread overview]
Message-ID: <20011213.122126.125897109.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.21.0112131413480.28370-100000@freak.distro.conectiva>
In-Reply-To: <20011212.192636.133010681.davem@redhat.com> <Pine.LNX.4.21.0112131413480.28370-100000@freak.distro.conectiva>
From: Marcelo Tosatti <marcelo@conectiva.com.br>
Date: Thu, 13 Dec 2001 14:14:18 -0200 (BRST)
I've already asked Linus about that and he told me that he is giving
higher priority to core changes now and wants to do the merges later...
That is going to be a lot to accumulate whenever the code change
priority goes back down, really.
To me it makes more sense to do a release or two making one of the
core changes, and fixing it up, then do a sync pass to get the bug
fixes piling up in 2.4.x
I think Linus's scheme is going to result in either a lot of missed
fixes or a lot of unnecessary work and headaches for some poor
person. :-)
next prev parent reply other threads:[~2001-12-13 20:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-13 3:09 ledzep37
2001-12-13 3:26 ` David S. Miller
2001-12-13 3:39 ` M. Edward (Ed) Borasky
2001-12-13 8:50 ` Alan Cox
2001-12-13 3:48 ` David S. Miller
2001-12-13 16:14 ` Marcelo Tosatti
2001-12-13 16:58 ` Dave Jones
2001-12-13 20:21 ` David S. Miller [this message]
-- strict thread matches above, loose matches on Subject: below --
2001-12-12 1:13 ledzep37
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=20011213.122126.125897109.davem@redhat.com \
--to=davem@redhat.com \
--cc=ledzep37@attbi.com \
--cc=linux-kernel@vger.kernel.org \
--cc=marcelo@conectiva.com.br \
/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
Powered by JetHome