From: Wolfgang Denk <wd@denx.de>
To: Tom Rini <trini@kernel.crashing.org>
Cc: Steven Scholz <steven.scholz@imc-berlin.de>,
LinuxPPC <linuxppc-embedded@lists.linuxppc.org>
Subject: Re: board specific defines in commproc.h !?!?
Date: Tue, 18 Jun 2002 00:28:07 +0200 [thread overview]
Message-ID: <20020617222812.3CCC0102FB@denx.denx.de> (raw)
In-Reply-To: Your message of "Mon, 17 Jun 2002 14:43:39 PDT." <20020617214339.GZ13541@opus.bloom.county>
Dear Tom,
in message <20020617214339.GZ13541@opus.bloom.county> you wrote:
>
> likely) for 2.4 and 2.5. And yes, an untested/lightly tested 2.5 patch
> is perfectly acceptible. 2.5 itself is only lightly tested (or not
> tested at all for some cases).
But don't you see the problem? Exactly this is what makes 2.5
unusable: it's a collection of lightly or not tested patches.
> I'm asking you (and everyone else) to submit new work for the community
> vs 2.5 before you submit it for 2.4. This has the bonus that the next
> stable release will have all of your fixes in it already and you won't
I don't see any bonus, but I do see additional (and most probably
wasted) efford.
Tom, let's stop here. I understand _what_ you say, and even parts of
the _why_, but it's not practical to me.
Wolfgang Denk
--
Software Engineering: Embedded and Realtime Systems, Embedded Linux
Phone: (+49)-8142-4596-87 Fax: (+49)-8142-4596-88 Email: wd@denx.de
After a time, you may find that "having" is not so pleasing a thing,
after all, as "wanting." It is not logical, but it is often true.
-- Spock, "Amok Time", stardate 3372.7
** Sent via the linuxppc-embedded mail list. See http://lists.linuxppc.org/
next parent reply other threads:[~2002-06-17 22:28 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020617214339.GZ13541@opus.bloom.county>
2002-06-17 22:28 ` Wolfgang Denk [this message]
2002-06-17 9:20 board specific defines in commproc.h !?!? Steven Scholz
2002-06-17 14:05 ` John W. Linville
2002-06-17 15:32 ` Tom Rini
2002-06-17 15:37 ` Steven Scholz
2002-06-17 15:49 ` Tom Rini
2002-06-17 16:01 ` Steven Scholz
2002-06-17 16:28 ` Tom Rini
2002-06-17 17:25 ` Wolfgang Denk
[not found] ` <20020617173550.GV13541@opus.bloom.county>
2002-06-17 17:46 ` Steven Scholz
2002-06-17 20:23 ` Wolfgang Denk
[not found] ` <3D106922.7026437A@imc-berlin.de>
2002-06-19 15:05 ` Tom Rini
2002-06-19 15:18 ` Steven Scholz
2002-06-19 15:25 ` Tom Rini
2002-06-19 15:33 ` Steven Scholz
2002-06-19 15:41 ` Tom Rini
2002-06-19 15:47 ` Steven Scholz
2002-06-19 15:51 ` Tom Rini
2002-06-19 21:11 ` Dan Malek
2002-06-19 21:22 ` Tom Rini
2002-06-20 16:32 ` Dan Malek
2002-06-19 22:15 ` Wolfgang Denk
2002-06-19 23:26 ` Conn Clark
2002-06-20 16:40 ` Dan Malek
[not found] ` <3D12F140.23BA447F@imc-berlin.de>
[not found] ` <15635.12386.415897.593660@argo.ozlabs.ibm.com>
2002-06-21 14:18 ` John Traill
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=20020617222812.3CCC0102FB@denx.denx.de \
--to=wd@denx.de \
--cc=linuxppc-embedded@lists.linuxppc.org \
--cc=steven.scholz@imc-berlin.de \
--cc=trini@kernel.crashing.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;
as well as URLs for NNTP newsgroup(s).