mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Dana Lacoste <dana.lacoste@peregrine.com>
To: David Schwartz <davids@webmaster.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: Is the BitKeeper network protocol documented?
Date: 21 Jan 2003 11:04:31 -0500	[thread overview]
Message-ID: <1043165072.1397.61.camel@dlacoste.ottawa.loran.com> (raw)
In-Reply-To: <20030120190037.AAA15691@shell.webmaster.com@whenever>

On Mon, 2003-01-20 at 14:00, David Schwartz wrote:

> 	I think you're entirely dropping the context. If the development of 
> a project is centered around a version control system, then that 
> version control system contains metainformation that is useful when 
> you're making modifications.

No, you're missing something very very very important here
(that someone else followed up with but you missed their point too)

The GPL was fundamentally designed to allow for the freedom to
modify the products that you have under the GPL.

This means that the source code to the product you have must be
in a form that is modifiable, and it must be in the 'preferred'
form for YOU to modify that code.

This has NOTHING to do with patches and tracking changes and
communicating with Linus.  This has to do with the code to the
software you use and YOUR ability to change it.

Thus you can take any release of Linux's source and add it into
BK or p4 or CVS or rcs/sccs and you can make your own changes to
that source code.  The binary you have was created from that
source code and the GPL protects your right to modify that source
code.

BK is merely a way that the product authors can manage their changelists
over time.  The BK information is not used in the build of the binary,
therefore it is not part of the binary and not having it is not
preventing you from modifying the source code to the binary you do have.
Even if you got it from Red Hat.

Dana Lacoste
Ottawa, Canada


  parent reply	other threads:[~2003-01-21 15:55 UTC|newest]

Thread overview: 61+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20030119235742.AAA13049%shell.webmaster.com@whenever>
2003-01-20  0:36 ` Valdis.Kletnieks
2003-01-20  1:05   ` David Schwartz
2003-01-20 14:28     ` Dana Lacoste
2003-01-20 19:00       ` David Schwartz
2003-01-20 19:31         ` David Lang
2003-01-20 20:19           ` David Schwartz
2003-01-20 20:40             ` John Bradford
2003-01-20 20:48             ` Andreas Dilger
2003-01-20 21:14               ` David Schwartz
2003-01-20 21:58                 ` John Bradford
2003-01-20 21:37               ` Sam Ravnborg
2003-01-20 21:41             ` Rik van Riel
2003-01-21 16:04         ` Dana Lacoste [this message]
2003-01-21 18:34           ` David Schwartz
2003-01-21 18:49             ` John Bradford
2003-01-21 18:58             ` Sam Ravnborg
2003-01-21 19:27             ` Dana Lacoste
2003-01-21 21:04               ` David Schwartz
2003-01-21 19:51             ` Hua Zhong
2003-01-22  7:10               ` Jamie Lokier
2003-01-22  7:21                 ` John Alvord
2003-01-22 15:18                 ` Larry McVoy
2003-01-22 15:27                   ` Dana Lacoste
2003-01-22 15:38                     ` Larry McVoy
2003-01-20  1:46   ` David Lang
2003-01-20  1:52   ` Andre Hedrick
2003-01-21 19:22 Larry McVoy
  -- strict thread matches above, loose matches on Subject: below --
2003-01-21  0:28 Cort Dougan
     [not found] <20030120194430.AAA20700%shell.webmaster.com@whenever>
2003-01-20 20:32 ` Valdis.Kletnieks
2003-01-20 21:27   ` David Schwartz
2003-01-21  8:51     ` Horst von Brand
2003-01-20 15:55 Theodore Ts'o
2003-01-20 18:53 ` David Schwartz
     [not found] <20030120010504.AAA18836%shell.webmaster.com@whenever>
2003-01-20  1:37 ` Valdis.Kletnieks
2003-01-18  6:22 Jamie Lokier
2003-01-18  4:33 Jamie Lokier
2003-01-18  4:57 ` David Schwartz
2003-01-18  5:10   ` Jamie Lokier
2003-01-18  7:23     ` David Schwartz
2003-01-18  5:02 ` Andrew Morton
2003-01-18  5:15   ` Jamie Lokier
2003-01-18  5:29 ` Larry McVoy
2003-01-18  6:11   ` Tupshin Harper
2003-01-18  6:20   ` Kevin Puetz
2003-01-18  6:39     ` Larry McVoy
2003-01-18  8:09   ` Jamie Lokier
2003-01-18  8:25     ` Andrew Morton
2003-01-18 14:22   ` Roman Zippel
2003-01-19 18:39     ` Andreas Dilger
2003-01-19 18:55       ` Jamie Lokier
2003-01-19 21:50       ` Roman Zippel
2003-01-19 23:26         ` Andreas Dilger
2003-01-19 23:57           ` David Schwartz
2003-01-20  0:20             ` Andreas Dilger
2003-01-20  0:38               ` David Schwartz
2003-01-20 15:52             ` Horst von Brand
2003-01-20 19:43               ` David Schwartz
2003-01-20 19:46               ` David Schwartz
2003-01-21  7:56                 ` Horst von Brand
2003-01-20 14:18           ` Roman Zippel
2003-01-22 12:24   ` Matthias Andree

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=1043165072.1397.61.camel@dlacoste.ottawa.loran.com \
    --to=dana.lacoste@peregrine.com \
    --cc=davids@webmaster.com \
    --cc=linux-kernel@vger.kernel.org \
    /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

all inboxes | Powered by JetHome®