public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Tupshin Harper <tupshin@tupshin.com>
To: Larry McVoy <lm@bitmover.com>
Cc: Andrea Arcangeli <andrea@suse.de>, linux-kernel@vger.kernel.org
Subject: Re: RFC - tarball/patch server in BitKeeper
Date: Mon, 15 Dec 2003 15:08:16 -0800	[thread overview]
Message-ID: <3FDE3EE0.6060101@tupshin.com> (raw)
In-Reply-To: <20031215224626.GD8130@work.bitmover.com>

Larry McVoy wrote:

>Sigh.  Tupshin, everyone hates these discussions and I'm in agreement with 
>them.  What you want to discuss isn't about kernel development, it's about
>building SCM systems.  There are better places to do that than here.  
>
>If you need clarification on whether you are violating our license, consult
>a lawyer.  
>  
>
I'm not asking for legal advice. I'm asking for bitkeeper's position on 
fair usage of data. You made a claim that seems to have zero backing in 
the bkl. I think asking for a justification of that claim is quite 
reasonable. I know for a fact that I'm not violating your license, 
because I'm not using your software and haven't agreed to your license. 
The implication you made was that certain other people are violating 
your license by exporting changesets publicly. If that is true, then 
that is highly relevant to this list. kernel.org, for example would have 
to remove changeset information such as 
http://www.kernel.org/pub/linux/kernel/v2.6/testing/cset/

-Tupshin

  reply	other threads:[~2003-12-15 23:09 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 [this message]
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=3FDE3EE0.6060101@tupshin.com \
    --to=tupshin@tupshin.com \
    --cc=andrea@suse.de \
    --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