From: "David S. Miller" <davem@redhat.com>
To: znmeb@aracnet.com
Cc: linux-kernel@vger.kernel.org
Subject: Re: __devexit_p() in linux-2.5.1-preX?
Date: Wed, 12 Dec 2001 19:48:42 -0800 (PST) [thread overview]
Message-ID: <20011212.194842.66059225.davem@redhat.com> (raw)
In-Reply-To: <Pine.LNX.4.33.0112121936180.22588-100000@shell1.aracnet.com>
In-Reply-To: <20011212.192636.133010681.davem@redhat.com> <Pine.LNX.4.33.0112121936180.22588-100000@shell1.aracnet.com>
From: "M. Edward (Ed) Borasky" <znmeb@aracnet.com>
Date: Wed, 12 Dec 2001 19:39:03 -0800 (PST)
On Wed, 12 Dec 2001, David S. Miller wrote:
> This brings up a more generic issue. It would really be nice to have
> someone who syncs up 2.5.X with the bug fixes going into the 2.4.x
> series. It really is needed, and it really is a boring and thankless
> job :-)
And the reason said boring thankless job can't be done by an automated
revision control system is??
Because it requires a human brain to deal with the conflicts.
Any fixes to the block layer is going to have this problem,
and once we go to kbuild 2.5 these kinds of conflicts will
be even larger.
I use a revision control system, and have done so for 6 or more years,
and I have to merge a lot of things by hand. It's not because I'm and
idiot, or that my revision control system sucks, it's simply because
interfaces and config/makefile format changes require by hand work.
next prev parent reply other threads:[~2001-12-13 3:49 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 [this message]
2001-12-13 16:14 ` Marcelo Tosatti
2001-12-13 16:58 ` Dave Jones
2001-12-13 20:21 ` David S. Miller
-- 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=20011212.194842.66059225.davem@redhat.com \
--to=davem@redhat.com \
--cc=linux-kernel@vger.kernel.org \
--cc=znmeb@aracnet.com \
/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