From: Larry McVoy <lm@bitmover.com>
To: Edgar Toernig <froese@gmx.de>
Cc: Larry McVoy <lm@bitmover.com>,
Daniel Phillips <phillips@bonn-fries.net>,
Timothy Covell <timothy.covell@ashavan.org>,
linux-kernel@vger.kernel.org
Subject: Re: RFC: Linux Bug Tracking & Feature Tracking DB
Date: Sat, 29 Dec 2001 15:45:20 -0800 [thread overview]
Message-ID: <20011229154520.D21760@work.bitmover.com> (raw)
In-Reply-To: <200112290657.fBT6vMSr008000@svr3.applink.net> <20011229105525.C19306@work.bitmover.com> <3C2E14AB.69CEA694@gmx.de> <E16KRjh-0000GP-00@starship.berlin> <3C2E4934.D582AB91@gmx.de> <20011229150247.A21733@work.bitmover.com> <3C2E51E9.A9B279D8@gmx.de>
In-Reply-To: <3C2E51E9.A9B279D8@gmx.de>; from froese@gmx.de on Sun, Dec 30, 2001 at 12:29:45AM +0100
> After that I heard nothing more from you. I got the impression that a
> libc5 system was not commercially interesting enough...
Huh. Well, it's easy enough to add that to the list of build machines,
I think I can build libc5 binaries on redhat52, and we support that.
> > And, it would be nice if you raised the issue with us rather than the
> > kernel list, they aren't going to build your BK image for you.
>
> I asked nobody to build a BK image for me. You are constantly misusing
> the lkml as a BK promotion facility.
If you feel that way, might I kindly suggest you add a simple rule to your
procmail filters and spare yourself (and the rest of the world) some pain?
I can show you how to do it if you don't know how, it would be no problem.
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2001-12-29 23:45 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
2001-12-29 6:53 RFC: Linux Bug Tracking & Feature Tracking DB Timothy Covell
2001-12-29 7:20 ` Anuradha Ratnaweera
2001-12-29 18:55 ` Larry McVoy
2001-12-29 19:08 ` Edgar Toernig
2001-12-29 22:13 ` Daniel Phillips
2001-12-29 22:52 ` Edgar Toernig
2001-12-29 23:02 ` Larry McVoy
2001-12-29 23:29 ` Edgar Toernig
2001-12-29 23:45 ` Larry McVoy [this message]
2001-12-29 19:16 ` Timothy Covell
2001-12-29 23:32 ` Stewart Smith
2001-12-29 23:45 ` Dave Jones
2001-12-30 5:24 ` Stewart Smith
2001-12-30 12:12 ` Dave Jones
2001-12-31 0:42 ` Richard Gooch
2001-12-31 0:44 ` H. Peter Anvin
2001-12-31 0:47 ` Richard Gooch
2001-12-31 0:52 ` H. Peter Anvin
2001-12-31 1:16 ` Richard Gooch
2001-12-31 4:58 ` H. Peter Anvin
2001-12-31 5:07 ` Richard Gooch
2001-12-31 0:47 ` Arnaldo Carvalho de Melo
2001-12-31 0:49 ` Dave Jones
2001-12-31 21:50 ` Rob Landley
2001-12-31 19:40 ` David Ford
2001-12-31 19:27 ` David Ford
2001-12-31 20:00 ` Dave Jones
2002-01-02 2:27 ` David Ford
2002-01-01 6:35 ` Horst von Brand
2002-01-02 2:46 ` David Ford
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=20011229154520.D21760@work.bitmover.com \
--to=lm@bitmover.com \
--cc=froese@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.net \
--cc=timothy.covell@ashavan.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