From: "David S. Miller" <davem@redhat.com>
To: jt@hpl.hp.com, jt@bougret.hpl.hp.com
Cc: marcelo@conectiva.com.br, linux-kernel@vger.kernel.org,
alan@lxorguk.ukuu.org.uk
Subject: Re: Linux 2.4.20-pre1
Date: Tue, 06 Aug 2002 10:13:08 -0700 (PDT) [thread overview]
Message-ID: <20020806.101308.30924385.davem@redhat.com> (raw)
In-Reply-To: <20020806171736.GC11313@bougret.hpl.hp.com>
From: Jean Tourrilhes <jt@bougret.hpl.hp.com>
Date: Tue, 6 Aug 2002 10:17:36 -0700
The second thing that bugs me is that because those patches
pass behind my back, they won't get applied to *both* 2.4.X and
2.5.X. Because of that, keeping 2.4.X and 2.5.X in synch is an
exercise in futility.
This is an old topic. If cleanups get submitted they are going
to go in. If this means that someone has to redo a patch, that
is just a part of life.
Nobody is "above the law", sort of speak, when it comes to these
things. Cleanups and compile warning fixes are not required to
go through the maintainer of a piece of code.
About IRDA wrt. 2.4.x vs 2.5.x, it requires a partial rewrite in 2.5.x
anyways so don't get worked up over it :)
next prev parent reply other threads:[~2002-08-06 17:23 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-06 0:21 Linux 2.4.20-pre1 Jean Tourrilhes
2002-08-06 12:33 ` Marcelo Tosatti
2002-08-06 17:17 ` Jean Tourrilhes
2002-08-06 16:31 ` Marcelo Tosatti
2002-08-06 17:24 ` Jean Tourrilhes
2002-08-06 17:13 ` David S. Miller [this message]
2002-08-06 18:48 ` Alan Cox
-- strict thread matches above, loose matches on Subject: below --
2002-08-15 17:28 Matt_Domsch
2002-08-11 21:12 Matt_Domsch
[not found] <200208062329.g76NTqP30962@devserv.devel.redhat.com.suse.lists.linux.kernel>
2002-08-07 10:01 ` Andi Kleen
2002-08-07 11:50 ` Alan Cox
2002-08-06 23:29 Alan Cox
2002-08-05 22:40 Marcelo Tosatti
2002-08-06 0:20 ` Ben Greear
2002-08-06 11:32 ` Marcelo Tosatti
2002-08-06 12:26 ` David S. Miller
2002-08-06 16:45 ` Ben Greear
2002-08-06 14:58 ` Jason Lunz
2002-08-06 15:03 ` CaT
2002-08-06 21:05 ` Adrian Bunk
2002-08-07 11:09 ` David S. Miller
2002-08-07 0:21 ` J.A. Magallon
2002-08-07 1:08 ` J.A. Magallon
2002-08-07 1:56 ` Bryan Whitehead
2002-08-07 3:35 ` Tim Hockin
2002-08-11 8:57 ` Erik Andersen
2002-08-11 9:16 ` Christoph Hellwig
2002-08-11 9:40 ` Erik Andersen
2002-08-11 9:46 ` Erik Andersen
2002-08-11 19:46 ` Alan Cox
2002-08-11 18:49 ` Erik Andersen
2002-08-12 19:29 ` Paul P Komkoff Jr
2002-08-11 10:56 ` Erik Andersen
2002-08-17 19:51 ` Adrian Bunk
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=20020806.101308.30924385.davem@redhat.com \
--to=davem@redhat.com \
--cc=alan@lxorguk.ukuu.org.uk \
--cc=jt@bougret.hpl.hp.com \
--cc=jt@hpl.hp.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