public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Larry McVoy <lm@bitmover.com>
To: Tupshin Harper <tupshin@tupshin.com>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Sun, 14 Dec 2003 19:46:27 -0800	[thread overview]
Message-ID: <20031215034627.GB16554@work.bitmover.com> (raw)
In-Reply-To: <3FDCFE17.5010309@tupshin.com>

On Sun, Dec 14, 2003 at 04:19:35PM -0800, Tupshin Harper wrote:
> >I'm sure you do, I've read your postings on various SCM mailing lists.
> >You'll have to get your test data elsewhere, sorry, we're not in the
> >business of helping you develop a competing product.  Using BK to do
> >that is a violation of the free use license and I'm sure you are aware
> >of that.  
> >
> Of course...that's the only reason why it's an issue.

Great, glad you understand that you are crossing the legal line.

> What are are effectively doing, then, is creating vendor lock-in based 
> on file format...a very Microsoftian approach. You are encouraging 
> developers to adopt your tool, but then telling them that if they ever 
> want to adopt a different tool, then they will have to forego using some 
> of the information that they created using your tool. So the decision of 
> which tool to be used becomes based on pain of switching, and not based 
> on technical merit. Hmmm.

What a pile of nonsense.  Let's translate this to reality.  You can't
figure out how to build the right answer and you have decided you need
access to internal information created by BitKeeper to reverse engineer
BitKeeper and you are complaining because we don't feel obligated to
give you that.

If you think you can create a better answer on your own, by all means,
do so, nobody is stopping you.  But whining that you aren't being helped
by the people who have figured it out is not exactly inspiring.  I can
assure you that I am not inspired to help you and I'm disgusted that yet
again an you have taken something that we are trying to do to help people
and turned it into a whine fest for your personal agenda.
-- 
---
Larry McVoy              lm at bitmover.com          http://www.bitmover.com/lm

  reply	other threads:[~2003-12-15  3:46 UTC|newest]

Thread overview: 35+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-14 17:21 RFC - tarball/patch server in BitKeeper Larry McVoy
2003-12-14 23:05 ` Keith Owens
2003-12-14 23:44   ` Larry McVoy
2003-12-15  0:25     ` Keith Owens
2003-12-15  3:47       ` Larry McVoy
2003-12-14 23:17 ` Tupshin Harper
2003-12-14 23:43   ` Larry McVoy
2003-12-15  0:19     ` Tupshin Harper
2003-12-15  3:46       ` Larry McVoy [this message]
2003-12-15  6:07         ` Tupshin Harper
2003-12-15 16:02           ` Larry McVoy
2003-12-15 19:52             ` Tupshin Harper
2003-12-15  6:31 ` Martin J. Bligh
2003-12-15 12:11   ` Sergey Vlasov
2003-12-15 13:27     ` Ben Collins
2003-12-15 16:24       ` Sergey Vlasov
2003-12-15 16:32         ` Larry McVoy
2003-12-15 18:31         ` Andrea Arcangeli
2003-12-15 18:58           ` Larry McVoy
2003-12-15 19:40             ` Andrea Arcangeli
2003-12-15 21:44               ` Larry McVoy
2003-12-15 22:02                 ` Andrea Arcangeli
2003-12-15 22:14                   ` Larry McVoy
2003-12-15 22:44                     ` Tupshin Harper
2003-12-15 23:13                       ` Andrea Arcangeli
2003-12-15 22:36                 ` Tupshin Harper
2003-12-15 22:46                   ` Larry McVoy
2003-12-15 23:08                     ` Tupshin Harper
2003-12-17  4:47                       ` Matthew D. Pitts
2003-12-15 15:42   ` Larry McVoy
2003-12-15 15:55     ` Martin J. Bligh
2003-12-15 23:18 ` Chris Frey
2003-12-21 20:02 ` Pavel Machek
2003-12-21 20:46   ` John Bradford
2003-12-24  1:49   ` Larry McVoy

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=20031215034627.GB16554@work.bitmover.com \
    --to=lm@bitmover.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=tupshin@tupshin.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