From: Larry McVoy <lm@bitmover.com>
To: Jerry McBride <mcbrides9@comcast.net>
Cc: Christoph Lameter <christoph@lameter.com>, linux-kernel@vger.kernel.org
Subject: Re: 2.5.10-dj1 compilation failure
Date: Sat, 27 Apr 2002 13:48:01 -0700 [thread overview]
Message-ID: <20020427134801.C31314@work.bitmover.com> (raw)
In-Reply-To: <20020427192459.P14743@suse.de> <Pine.LNX.4.44.0204271033010.5612-100000@k2-400.lameter.com> <20020427140950.789adbb1.mcbrides9@comcast.net>
On Sat, Apr 27, 2002 at 02:09:50PM -0400, Jerry McBride wrote:
> On Sat, 27 Apr 2002 10:35:55 -0700 (PDT) Christoph Lameter
> <christoph@lameter.com> wrote:
> > That stuff might be useful in a CVS or BK() source code archive.
> > What is the purpose of releasing a kernel tarball that does not compile?
> > Kernel tarball are there to be compiled and tried out ....
>
> MAN! You said a mouth full. I've found syntax errors, misspellings and
> just plain old junk text in the make files of 2.5.10.
>
> I appreciate the efforts going into the new kernel tree. I really look
> forward to it becoming main stream... but MY GOD, at least I wish they
> would try to compile the thing BEFORE it gets posted for download!
I appreciate your efforts at being a considerate human being.
I really look forward to you becoming part of the pleasant set of human
beings... but MY GOD, at least I wish you would do some work yourself
BEFORE posting a complaint!
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2002-04-27 20:48 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-04-27 17:18 2.5.10-dj1 compilation failure Christoph Lameter
2002-04-27 17:24 ` Dave Jones
2002-04-27 17:35 ` Christoph Lameter
2002-04-27 17:47 ` Dave Jones
2002-04-27 21:44 ` Martin Dalecki
2002-04-27 18:09 ` Jerry McBride
2002-04-27 19:14 ` Rik van Riel
2002-04-27 20:48 ` Larry McVoy [this message]
[not found] <Pine.LNX.4.44.0204271033010.5612-100000@k2-400.lameter.com >
2002-04-27 17:50 ` Anton Altaparmakov
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=20020427134801.C31314@work.bitmover.com \
--to=lm@bitmover.com \
--cc=christoph@lameter.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcbrides9@comcast.net \
/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