The Linux Kernel Mailing List
 help / color / mirror / Atom feed
From: Daniel Phillips <phillips@bonn-fries.net>
To: dean gaudet <dean-list-linux-kernel@arctic.org>
Cc: Larry McVoy <lm@bitmover.com>, Jeff Garzik <garzik@havoc.gtf.org>,
	<linux-kernel@vger.kernel.org>
Subject: Re: double-standard? (Re: [PATCH] Remove Bitkeeper documentation from Linux tree)
Date: Sun, 21 Apr 2002 22:49:10 +0200	[thread overview]
Message-ID: <E16zOGm-0001Lz-00@starship> (raw)
In-Reply-To: <Pine.LNX.4.44.0204221315430.14415-100000@twinlark.arctic.org>

On Monday 22 April 2002 22:37, dean gaudet wrote:
> i happen to put food on my table working at a hardware company; larry puts
> food on his working at a software company.  i happen to work at the same
> hardware company as linus does:  transmeta.  every kernel for the past,
> uh, 6 or 7 years, has included an advertisement for transmeta.  could we
> possibly conceive of removing all references to transmeta from the kernel,
> mailing lists and archives?

How big is the Transmeta ad?  Does it have its own file?  Would you be
satisfied if Bitkeeper had the same size advertisement as Transmeta?

-- 
Daniel

  reply	other threads:[~2002-04-22 20:48 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20020421101731.D10525@work.bitmover.com>
2002-04-21 17:22 ` [PATCH] Remove Bitkeeper documentation from Linux tree Jeff Garzik
2002-04-20 17:48   ` Daniel Phillips
2002-04-21 17:55     ` Jeff Garzik
2002-04-20 18:07       ` Daniel Phillips
2002-04-20 18:13       ` Daniel Phillips
2002-04-21 18:15         ` Jeff Garzik
2002-04-20 18:26           ` Daniel Phillips
2002-04-21 18:40             ` Jeff Garzik
2002-04-21 18:21         ` Larry McVoy
2002-04-20 18:29           ` Daniel Phillips
2002-04-21 18:36             ` Larry McVoy
2002-04-20 18:46               ` Daniel Phillips
2002-04-21 19:07                 ` Larry McVoy
2002-04-21 14:39               ` Daniel Phillips
2002-04-21 18:38             ` yodaiken
2002-04-21 18:08     ` Larry McVoy
2002-04-20 18:15       ` Daniel Phillips
2002-04-21 19:06         ` dean gaudet
2002-04-21 14:53           ` Daniel Phillips
2002-04-22 17:03             ` Jeff Garzik
2002-04-21 17:27               ` Daniel Phillips
2002-04-22 17:30                 ` Larry McVoy
2002-04-21 17:47                   ` Daniel Phillips
2002-04-22 17:40                 ` Jeff Garzik
2002-04-21 17:57                   ` Daniel Phillips
2002-04-22 20:47                     ` Jeff Garzik
2002-04-21 20:54                       ` Daniel Phillips
2002-04-22 22:04                       ` Davide Libenzi
2002-04-22 22:17                         ` There is no cabal (was: the BK flamewar) Jeff Garzik
2002-04-22 23:22                           ` Davide Libenzi
2002-04-22 23:27                             ` Jeff Garzik
2002-04-22 20:37             ` double-standard? (Re: [PATCH] Remove Bitkeeper documentation from Linux tree) dean gaudet
2002-04-21 20:49               ` Daniel Phillips [this message]
2002-04-21 20:22           ` [PATCH] Remove Bitkeeper documentation from Linux tree Andrew Morton
2002-04-22  0:01             ` Larry McVoy
2002-04-22 20:32             ` Jeff Garzik

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=E16zOGm-0001Lz-00@starship \
    --to=phillips@bonn-fries.net \
    --cc=dean-list-linux-kernel@arctic.org \
    --cc=garzik@havoc.gtf.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lm@bitmover.com \
    /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