From: Edgar Toernig <froese@gmx.de>
To: Larry McVoy <lm@bitmover.com>
Cc: 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: Sun, 30 Dec 2001 00:29:45 +0100 [thread overview]
Message-ID: <3C2E51E9.A9B279D8@gmx.de> (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>
Larry McVoy wrote:
>
> On Sat, Dec 29, 2001 at 11:52:36PM +0100, Edgar Toernig wrote:
> > Daniel Phillips wrote:
> > >
> > > On December 29, 2001 08:08 pm, Edgar Toernig wrote:
> > > > Larry McVoy wrote:
> > > > >
> > > > > The data in it is the current BitKeeper bug list (feel free to fix
> > > > > some :-)
> > > >
> > > > Bah! Debugging and patching binaries isn't fun!
> > >
> > > Check the site, he provides the source.
> >
> > Just checked it again: no sources. Only binaries. None of them
> > will run on my system. Last time I asked for the sources my
> > request was rejected.
>
> The only interaction with you that I've ever had, according to my outbox,
> is on Date: Mon, 30 Oct 2000 15:38:43 -0800 where you asked about BK,
> said there wasn't an image for you platform, I asked what platform, and
> so far haven't heard back, at least I have no record of it.
The answer was sent 1 minute after your reply. Here it is again:
----------------
> Date: Tue, 31 Oct 2000 00:36:40 +0100
> From: Edgar Toernig <froese@gmx.de>
> To: Larry McVoy <lm@bitmover.com>
> Subject: Re: Source of Bitkeeper
> Message-ID: <39FE0608.7C11302E@gmx.de>
> References: <39FE034C.F6658D5A@gmx.de> <20001030153843.C31369@work.bitmover.com>
>
> Larry McVoy wrote:
> >
> > On Tue, Oct 31, 2000 at 12:25:00AM +0100, Edgar Toernig wrote:
> > > is the source code of Bitkeeper somewhere to download?
> > > There's no binary image for my system. And, I prefer
> > > sources anyway.
> >
> > Which platform is it?
>
> An old linux system with libc5.
>
> Ciao, ET.
------------------
After that I heard nothing more from you. I got the impression that a
libc5 system was not commercially interesting enough...
> 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. And when you raise the impression
that sources are available I'll correct that. Pretty simple.
Ciao, ET.
Reply-To set...
next prev parent reply other threads:[~2001-12-29 23:31 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 [this message]
2001-12-29 23:45 ` Larry McVoy
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=3C2E51E9.A9B279D8@gmx.de \
--to=froese@gmx.de \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--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