From: Larry McVoy <lm@bitmover.com>
To: Pavel Machek <pavel@suse.cz>
Cc: Larry McVoy <lm@bitmover.com>, Andrea Arcangeli <andrea@suse.de>,
linux-kernel@vger.kernel.org
Subject: Re: Inappropriate signatures
Date: Sat, 13 Sep 2003 09:49:56 -0700 [thread overview]
Message-ID: <20030913164956.GA9246@work.bitmover.com> (raw)
In-Reply-To: <20030913153956.GA527@elf.ucw.cz>
Other people may not agree with your view on this one Pavel. Most people
read that signature and saw it as a negative comment about BitKeeper.
People have told me they believe that if BitMover isn't getting benefit
from the free use of BK, free BK will go away. People don't want to have
to depend on my goodwill, they want BitMover to derive benefit so that
my goodwill doesn't matter, it's just smart business to give BK away.
If that is really what people here think then that means there has to
be some benefit for BitMover. One of the benefits is that we get to say
that the kernel team uses it and get some marketing advantage out of that.
But that benefit diminishes if what people are saying is negative.
It makes sense that people are uneasy about depending on BK given the
amount of work it takes to provide it and the amount of grief we take
for providing it. I don't know why I didn't see that earlier, it's an
unstable situation.
I know there are some people who will never be happy until everything
is GPLed, I can't help those people other than provide the gateway.
In return, those people need to stop whining, the gateway has to be
enough.
For the rest of the people, I'm looking for suggestions on how to make
this situation more stable. It took me a while but I can see why you
are nervous, I'd be nervous in your position. I'm nervous about doing
any real marketing of the kernel's use of BK because I figured it would
lead to more flame wars. I'm starting to think that if we were doing
that it might actually lead to less flames, based on the theory that we
would then need you so you continue to get BK for free. If you have an
opinion on that I'd like to know it.
On Sat, Sep 13, 2003 at 05:39:56PM +0200, Pavel Machek wrote:
> Hi!
>
> > We're providing the service which enables all of the below and without
> > our good will that service is at risk.
>
> Eh? You are providing a service and he provides you advertising. I
> can't see anything about slamming you. I guess that Andrea does not
> think about kernel developing as a business, so it is not really
> targeted at you.
>
> But anyway its *his* signature.
> Pavel
>
> > > /*
> > > * If you refuse to depend on closed software for a critical
> > > * part of your business, these links may be useful:
> > > *
> > > * rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.5/
> > > * rsync.kernel.org::pub/scm/linux/kernel/bkcvs/linux-2.4/
> > > * http://www.cobite.com/cvsps/
> > > *
> > > * svn://svn.kernel.org/linux-2.6/trunk
> > > * svn://svn.kernel.org/linux-2.4/trunk
> > > */
>
> --
> When do you have a heart between your knees?
> [Johanka's followup: and *two* hearts?]
--
---
Larry McVoy lm at bitmover.com http://www.bitmover.com/lm
next prev parent reply other threads:[~2003-09-13 16:50 UTC|newest]
Thread overview: 67+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-09-09 17:30 Efficient IPC mechanism on Linux Luca Veraldi
2003-09-09 21:17 ` Alan Cox
2003-09-09 21:57 ` Luca Veraldi
2003-09-09 23:11 ` Alan Cox
2003-09-10 9:04 ` Luca Veraldi
2003-09-10 12:56 ` Alan Cox
[not found] ` <20030909175821.GL16080@Synopsys.COM>
[not found] ` <001d01c37703$8edc10e0$36af7450@wssupremo>
[not found] ` <20030910064508.GA25795@Synopsys.COM>
2003-09-10 9:18 ` Luca Veraldi
2003-09-10 9:23 ` Arjan van de Ven
2003-09-10 9:40 ` Luca Veraldi
2003-09-10 9:44 ` Arjan van de Ven
2003-09-10 10:09 ` Luca Veraldi
2003-09-10 10:14 ` Arjan van de Ven
2003-09-10 10:25 ` Luca Veraldi
2003-09-12 18:41 ` Timothy Miller
2003-09-12 19:05 ` Luca Veraldi
2003-09-12 22:37 ` Alan Cox
2003-09-10 12:50 ` Alan Cox
2003-09-10 19:16 ` Shawn
2003-09-10 20:05 ` Rik van Riel
2003-09-17 9:52 ` Rik's list of CS challenges Terje Eggestad
2003-09-17 13:40 ` Alan Cox
2003-09-18 8:26 ` Helge Hafting
2003-09-10 12:47 ` Efficient IPC mechanism on Linux Alan Cox
2003-09-10 13:56 ` Luca Veraldi
2003-09-10 15:59 ` Alan Cox
2003-09-10 9:52 ` Jamie Lokier
2003-09-10 10:07 ` Arjan van de Ven
2003-09-10 10:17 ` Luca Veraldi
2003-09-10 10:37 ` Jamie Lokier
2003-09-10 10:41 ` Arjan van de Ven
2003-09-10 10:54 ` Luca Veraldi
2003-09-10 10:54 ` Arjan van de Ven
2003-09-10 11:16 ` Nick Piggin
2003-09-10 11:30 ` Luca Veraldi
2003-09-10 11:44 ` Nick Piggin
2003-09-10 12:14 ` Luca Veraldi
2003-09-10 12:42 ` Alan Cox
2003-09-10 10:11 ` Luca Veraldi
2003-09-10 19:24 ` Pavel Machek
2003-09-10 19:40 ` Jamie Lokier
2003-09-10 21:35 ` Pavel Machek
2003-09-10 22:06 ` Jamie Lokier
2003-09-10 11:52 ` Alex Riesen
2003-09-10 12:14 ` Luca Veraldi
2003-09-10 12:11 ` Alex Riesen
2003-09-10 12:29 ` Luca Veraldi
2003-09-10 12:28 ` Alex Riesen
2003-09-10 12:36 ` Luca Veraldi
2003-09-10 12:36 ` Alex Riesen
2003-09-10 13:33 ` Gábor Lénárt
2003-09-10 14:04 ` Luca Veraldi
2003-09-10 14:21 ` Stewart Smith
2003-09-10 14:39 ` Luca Veraldi
2003-09-10 16:59 ` Andrea Arcangeli
2003-09-10 17:05 ` Andrea Arcangeli
2003-09-10 17:21 ` Luca Veraldi
2003-09-10 17:41 ` Andrea Arcangeli
2003-09-10 17:39 ` Martin Konold
2003-09-10 18:01 ` Andrea Arcangeli
2003-09-10 18:05 ` Martin Konold
2003-09-10 18:31 ` Chris Friesen
2003-09-10 18:08 ` Inappropriate signatures Larry McVoy
2003-09-10 18:52 ` Jamie Lokier
2003-09-10 19:54 ` rsync head? [was inappropriate signatures] Joe Perches
2003-09-13 15:39 ` Inappropriate signatures Pavel Machek
2003-09-13 16:49 ` Larry McVoy [this message]
-- strict thread matches above, loose matches on Subject: below --
2003-09-10 18:44 John Bradford
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=20030913164956.GA9246@work.bitmover.com \
--to=lm@bitmover.com \
--cc=andrea@suse.de \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@suse.cz \
/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