From: Larry McVoy <lm@bitmover.com>
To: Pavel Machek <pavel@ucw.cz>
Cc: Larry McVoy <lm@bitmover.com>, linux-kernel@vger.kernel.org
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Tue, 23 Dec 2003 17:49:19 -0800 [thread overview]
Message-ID: <20031224014918.GA25527@work.bitmover.com> (raw)
In-Reply-To: <20031221200257.GA15772@elf.ucw.cz>
Hey, Pavel, do me a favor and take me off the cc list. I've unsubscribed
from the Linux kernel list, this is a good example of why. No sense of
humor on your part, and you are whining about a license on a 200 line
chunk of code. Any decent programmer could have reimplemented it in
less time than it took you to complain.
On Sun, Dec 21, 2003 at 09:02:57PM +0100, Pavel Machek wrote:
> Hi!
>
> > and patches. The idea is to make it possible for all trees hosted by
> > bkbits.net provide access to the data with a free client (included
> ~~~~
> > below
> > in prototype form).
>
> Unfortunately that is not free client for any reasonable definition of
> "free"; which matters, because it means that tarball.c is not getting
> into any distribution in any form. Someone will simply have to
> reimplement it.
> Pavel
>
> > /*
> > * tarball.c copyright (c) 2003 BitMover, Inc.
> > *
> > * Licensed under the NWL - No Whining License.
> > *
> > * You may use this, modify this, redistribute this provided you agree:
> > * - not to whine about this product or any other products from BitMover, Inc.
> > * - that there is no warranty of any kind.
> > * - retain this copyright in full.
> > */
>
> --
> 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
prev parent reply other threads:[~2003-12-24 1:51 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
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 [this message]
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=20031224014918.GA25527@work.bitmover.com \
--to=lm@bitmover.com \
--cc=linux-kernel@vger.kernel.org \
--cc=pavel@ucw.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