From: Pavel Machek <pavel@suse.cz>
To: Dave Jones <davej@suse.de>,
Daniel Phillips <phillips@bonn-fries.net>,
Anton Altaparmakov <aia21@cantab.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree (fwd)
Date: Sat, 20 Apr 2002 23:49:19 +0200 [thread overview]
Message-ID: <20020420214919.GC10549@elf.ucw.cz> (raw)
----- Forwarded message from Pavel Machek <pavel@suse.cz> -----
To: Dave Jones <davej@suse.de>, Daniel Phillips <phillips@bonn-fries.net>,
Anton Altaparmakov <aia21@cantab.net>
Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree
In-Reply-To: <E16ybpZ-0000V4-00@starship> <20020420191940.D856@suse.de>
Content-Disposition: inline
In-Reply-To: <20020420191940.D856@suse.de>
User-Agent: Mutt/1.3.28i
X-Warning: Reading this can be dangerous to your mental health.
Hi!
> > Oh I don't disagree at all. Bitkeeper is a big improvement over what
> > existed before. But it is proprietary. Which other tool in the tool chain
> > is proprietary?
>
> Film at 11: proprietory tool used in Linux.
> Maybe we should back out all those fixes the Stanford people found with
> their checker ? Maybe we should back out the x86-64 port seeing as
> it
Standford checker was proprietary?
> was (partly) done with a commercial simulator?
That's another case; doing development on proprietary CPU is okay, so
doing development on emulator (== CPU equivalent) should be okay, too.
Pavel
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
----- End forwarded message -----
--
(about SSSCA) "I don't say this lightly. However, I really think that the U.S.
no longer is classifiable as a democracy, but rather as a plutocracy." --hpa
reply other threads:[~2002-04-20 21:50 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20020420214919.GC10549@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=aia21@cantab.net \
--cc=davej@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=phillips@bonn-fries.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