From: Jeff Garzik <garzik@havoc.gtf.org>
To: Daniel Phillips <phillips@bonn-fries.net>
Cc: dean gaudet <dean-list-linux-kernel@arctic.org>,
Larry McVoy <lm@bitmover.com>,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] Remove Bitkeeper documentation from Linux tree
Date: Mon, 22 Apr 2002 16:47:28 -0400 [thread overview]
Message-ID: <20020422164728.H20999@havoc.gtf.org> (raw)
In-Reply-To: <Pine.LNX.4.44.0204211158160.30929-100000@twinlark.arctic.org> <E16zL7i-0001I2-00@starship> <20020422134059.B11216@havoc.gtf.org> <E16zLb1-0001IX-00@starship>
On Sun, Apr 21, 2002 at 07:57:55PM +0200, Daniel Phillips wrote:
> On Monday 22 April 2002 19:40, Jeff Garzik wrote:
> > On Sun, Apr 21, 2002 at 07:27:37PM +0200, Daniel Phillips wrote:
> > > 1) It would be equally as useful as a URL
> >
> > Maybe 5% less useful or so. There are reasons we move other
> > (non-controversial) docs into the kernel source. 100% of these docs can
> > be URLs.
> >
> > > 2) It would not consume download bandwidth
> >
> > This is a silly argument that dean gaudet dismembered. It's 12K
> > compressed and not your main argument at all.
> >
> >
> > > 3) It would show some sensitivity to the concerns of those who are
> > > uncomfortable with the license.
> >
> > I agree.
> >
> > So, I believe points #1 and #2 are silly, and #3 is your core argument.
>
> I think you stated that #1 is only 5% silly, by implication, 95% unsilly.
> Two out of three ain't bad.
I will grant you that :) but clarify:
Making is a URL is no big deal and shouldn't be a point of discussion,
as I think #2 is no big deal and shouldn't be a point of discussion.
The real question, as I understand it, is whether or not the kernel doc
should be in the kernel source or not. If the answer is 'no', then I
fully support making it a URL, or printing it out the back of
phonebooks, or whatever means of distribution :)
But I am arguing that the answer 'no' has not been justified yet...
> > And I agree that it would show sensitivity towards those people who
> > dislike the BK license.
> >
> > That said, I still think removing the doc is a hideously wrong thing
> > to do.
>
> I agree. (/me listens for sound of garzik hitting floor) The doc was never
> to be removed, it was to be moved. Read the original mail please. I repeat:
> I *like* your docs, in fact I think they are excellent docs. I just don't
> like to see them sitting in Documentation, for reasons we've been over in
> some detail.
This is really a semantic argument... I shorten "removing from kernel
sources" as "removing", because (correct me here) we are discussing what
we want to see in the kernel sources, and what we do not want to see in
the kernel sources.
Even without an official web site, the BK doc would live on in kernel
archives if nowhere else.
If it makes things more clear, I can use my same arguments, and do a
search-n-replace of "remove from kernel sources" to "move from kernel
sources to elsewhere." To me, it's the same thing.
> > I see the action of BK doc removal as encouraging some strict
> > notion of what we can and cannot discuss, inside the kernel sources.
> > _That_ is the free speech aspect.
> >
> > I see enforcing a strict notion of acceptable speech in the kernel
> > sources as a very bad thing for the Linux project.
> >
> > I'm not asking you to agree -- but do you even understand my viewpoint here?
>
> I do. I don't agree with you that any of this has something to do with free
> speech, but I'm willing to accept that you view the kernel source as a kind of
> podium.
I conjecture, then, that moving the BK doc to satisfy sensitivies is
also acknowledge of the kernel sources as a podium :)
> > > I really don't see how changing out the files for a url qualifies as
> > > the "worst way" of addressing the issue. If Larry unretracts his offer
> > > to host the files - and I fully expect he will do that after some period
> > > of indulging in his wounded bird act - then by definition the documentation
> > > will always be available exactly when and where needed. Is there *anybody*
> > > here who'd have further license-related complaints about Bitkeeper if that
> > > were done? (Speak or forever hold your peace.)
> >
> > First, I can host the doc. And will, if there is justification.
> > I do not see a justification. Larry is irrelevant.
>
> To this discussion? Debatable. I'll go with you on that for now though, and
> see where it leads.
hehe
> > Second, I guarantee that license-related complaints about BitKeeper will
> > continue to exist, regardless of the doc's location. Moving the doc
> > does absolutely nothing to assauge bad feelings about the BK license.
>
> It would for me, others mileage may vary.
Interesting. And I will claim up-front that I don't understand this
one bit. BitKeeper would still be in use with its odious license,
and people will still say the "BitKeeper mafia" exists, even if the
document is moved.
Jeff
next prev parent reply other threads:[~2002-04-22 20:47 UTC|newest]
Thread overview: 186+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20020421101731.D10525@work.bitmover.com>
2002-04-21 17:22 ` Jeff Garzik
2002-04-20 17:48 ` Daniel Phillips
2002-04-21 17:55 ` Jeff Garzik
2002-04-20 18:07 ` Daniel Phillips
2002-04-20 18:13 ` Daniel Phillips
2002-04-21 18:15 ` Jeff Garzik
2002-04-20 18:26 ` Daniel Phillips
2002-04-21 18:40 ` Jeff Garzik
2002-04-21 18:21 ` Larry McVoy
2002-04-20 18:29 ` Daniel Phillips
2002-04-21 18:36 ` Larry McVoy
2002-04-20 18:46 ` Daniel Phillips
2002-04-21 19:07 ` Larry McVoy
2002-04-21 14:39 ` Daniel Phillips
2002-04-21 18:38 ` yodaiken
2002-04-21 18:08 ` Larry McVoy
2002-04-20 18:15 ` Daniel Phillips
2002-04-21 19:06 ` dean gaudet
2002-04-21 14:53 ` Daniel Phillips
2002-04-22 17:03 ` Jeff Garzik
2002-04-21 17:27 ` Daniel Phillips
2002-04-22 17:30 ` Larry McVoy
2002-04-21 17:47 ` Daniel Phillips
2002-04-22 17:40 ` Jeff Garzik
2002-04-21 17:57 ` Daniel Phillips
2002-04-22 20:47 ` Jeff Garzik [this message]
2002-04-21 20:54 ` Daniel Phillips
2002-04-22 22:04 ` Davide Libenzi
2002-04-22 22:17 ` There is no cabal (was: the BK flamewar) Jeff Garzik
2002-04-22 23:22 ` Davide Libenzi
2002-04-22 23:27 ` Jeff Garzik
2002-04-22 20:37 ` double-standard? (Re: [PATCH] Remove Bitkeeper documentation from Linux tree) dean gaudet
2002-04-21 20:49 ` Daniel Phillips
2002-04-21 20:22 ` [PATCH] Remove Bitkeeper documentation from Linux tree Andrew Morton
2002-04-22 0:01 ` Larry McVoy
2002-04-22 20:32 ` Jeff Garzik
2002-04-22 18:37 Jonathan A. George
2002-04-22 18:58 ` Jeff Garzik
2002-04-22 19:19 ` Jonathan A. George
2002-04-22 19:51 ` Alexander Viro
2002-04-22 19:56 ` Jonathan A. George
2002-04-22 20:13 ` Alexander Viro
2002-04-22 19:52 ` Jeff Garzik
2002-04-22 21:53 ` Jonathan A. George
2002-04-22 19:47 ` Anton Altaparmakov
2002-04-22 19:54 ` Jeff Garzik
2002-04-22 21:13 ` Rik van Riel
-- strict thread matches above, loose matches on Subject: below --
2002-04-19 15:12 Daniel Phillips
2002-04-20 15:52 ` Jeff Garzik
2002-04-20 16:16 ` Roman Zippel
2002-04-20 16:25 ` David Lang
2002-04-20 17:05 ` Roman Zippel
2002-04-20 17:16 ` Linus Torvalds
2002-04-20 16:25 ` Jeff Garzik
2002-04-19 16:33 ` Daniel Phillips
2002-04-20 16:56 ` Linus Torvalds
2002-04-19 17:17 ` Daniel Phillips
2002-04-20 17:35 ` Linus Torvalds
2002-04-20 17:38 ` Thunder from the hill
2002-04-21 2:26 ` Ian Molton
2002-04-20 17:19 ` Roman Zippel
2002-04-20 21:03 ` Jeff Garzik
2002-04-20 21:36 ` Skip Ford
2002-04-20 21:40 ` Rik van Riel
2002-04-20 23:14 ` Larry McVoy
2002-04-20 21:53 ` Jeff Garzik
2002-04-21 0:04 ` Roman Zippel
2002-04-21 0:17 ` Larry McVoy
2002-04-21 9:22 ` Jochen Friedrich
2002-04-21 10:05 ` Thunder from the hill
2002-04-21 10:17 ` Thunder from the hill
2002-04-21 11:10 ` Anton Altaparmakov
2002-04-21 16:46 ` Jochen Friedrich
2002-04-21 17:00 ` Larry McVoy
2002-04-21 17:05 ` Anton Altaparmakov
2002-04-21 17:14 ` Larry McVoy
2002-04-21 13:18 ` Rik van Riel
2002-04-21 13:41 ` yodaiken
2002-04-21 16:50 ` Jochen Friedrich
2002-04-21 17:18 ` yodaiken
2002-04-21 15:17 ` Jeff Garzik
2002-04-21 16:32 ` Jeff Garzik
2002-04-20 16:46 ` Daniel Phillips
2002-04-21 16:57 ` Jeff Garzik
2002-04-20 17:11 ` Daniel Phillips
2002-04-22 12:06 ` Roman Zippel
2002-04-22 16:39 ` Jeff Garzik
2002-04-23 13:49 ` Roman Zippel
2002-04-23 14:51 ` Larry McVoy
2002-04-22 15:29 ` Daniel Phillips
2002-04-23 17:00 ` Rik van Riel
2002-04-23 18:12 ` Roman Zippel
2002-04-23 15:13 ` Roman Zippel
2002-04-23 15:17 ` Larry McVoy
2002-04-23 15:35 ` Roman Zippel
2002-04-23 15:37 ` Larry McVoy
2002-04-23 16:04 ` Roman Zippel
2002-04-23 17:01 ` Rik van Riel
2002-04-23 17:06 ` Roman Zippel
2002-04-23 15:05 ` Rik van Riel
2002-04-23 15:27 ` Roman Zippel
2002-04-21 2:30 ` Ian Molton
2002-04-21 15:33 ` Jeff Garzik
2002-04-20 15:46 ` Daniel Phillips
2002-04-21 15:59 ` Jeff Garzik
2002-04-21 23:36 ` Ian Molton
2002-04-26 21:58 ` Rik van Riel
2002-04-20 16:37 ` Linus Torvalds
2002-04-19 16:45 ` Daniel Phillips
2002-04-20 16:54 ` Alexander Viro
2002-04-21 2:36 ` Ian Molton
2002-04-20 15:54 ` Jeff Garzik
2002-04-20 16:29 ` Nils Philippsen
2002-04-20 16:56 ` Jeff Garzik
2002-04-21 2:38 ` Ian Molton
2002-04-20 16:13 ` Anton Altaparmakov
2002-04-19 16:21 ` Daniel Phillips
2002-04-20 16:51 ` Anton Altaparmakov
2002-04-19 17:05 ` Daniel Phillips
2002-04-20 17:09 ` Linus Torvalds
2002-04-19 17:32 ` Daniel Phillips
2002-04-20 17:51 ` Linus Torvalds
2002-04-19 21:02 ` Daniel Phillips
2002-04-20 21:07 ` Jeff Garzik
2002-04-19 22:01 ` Daniel Phillips
2002-04-20 22:20 ` Jeff Garzik
2002-04-19 22:34 ` Daniel Phillips
2002-04-20 22:54 ` Jeff Garzik
2002-04-21 1:41 ` Rob Landley
2002-04-20 15:44 ` Daniel Phillips
2002-04-21 15:52 ` Rob Landley
2002-04-21 15:59 ` Russell King
2002-04-20 16:10 ` Daniel Phillips
2002-04-21 16:15 ` Russell King
2002-04-21 16:15 ` Jeff Garzik
2002-04-21 16:02 ` arjan
2002-04-20 22:30 ` Stelian Pop
2002-04-21 2:46 ` Ian Molton
2002-04-20 22:37 ` Russell King
2002-04-20 23:15 ` Kenneth Johansson
2002-04-20 17:05 ` Daniel Phillips
2002-04-21 17:15 ` Jeff Garzik
2002-04-21 1:38 ` Oliver Xymoron
2002-04-21 15:32 ` Jeff Garzik
2002-04-20 22:00 ` Stevie O
2002-04-20 22:14 ` Anton Altaparmakov
2002-04-21 2:48 ` Ian Molton
2002-04-20 22:31 ` Jeff Garzik
2002-04-20 17:51 ` Larry McVoy
2002-04-19 18:27 ` Daniel Phillips
2002-04-20 17:51 ` Rob Landley
2002-04-20 18:41 ` Jeff Garzik
2002-04-20 17:15 ` Jeff Garzik
2002-04-20 17:19 ` Dave Jones
2002-04-20 17:58 ` Eric W. Biederman
2002-04-20 18:35 ` Anton Altaparmakov
2002-04-20 18:13 ` Rik van Riel
2002-04-19 19:43 ` Daniel Phillips
2002-04-20 20:04 ` Jeff Garzik
2002-04-21 2:53 ` Ian Molton
2002-04-21 1:46 ` Rob Landley
2002-04-21 15:51 ` Jeff Garzik
2002-04-21 16:26 ` Tigran Aivazian
2002-04-20 16:34 ` Daniel Phillips
2002-04-21 16:27 ` Richard Gooch
2002-04-20 16:36 ` Daniel Phillips
2002-04-21 16:45 ` Richard Gooch
2002-04-20 17:41 ` Larry McVoy
2002-04-19 18:07 ` Daniel Phillips
2002-04-20 17:53 ` Eric W. Biederman
2002-04-19 18:15 ` Daniel Phillips
2002-04-20 18:44 ` Eric W. Biederman
2002-04-19 19:22 ` Daniel Phillips
2002-04-20 18:48 ` Russell King
2002-04-19 19:19 ` Daniel Phillips
2002-04-21 2:57 ` Ian Molton
2002-04-21 2:56 ` Arnaldo Carvalho de Melo
2002-04-21 3:46 ` Ian Molton
2002-04-21 3:43 ` Arnaldo Carvalho de Melo
2002-04-21 15:36 ` Jeff Garzik
2002-04-21 9:28 ` Jochen Friedrich
2002-04-21 15:53 ` Arnaldo Carvalho de Melo
2002-04-21 18:11 ` John Alvord
2002-04-21 18:15 ` Arnaldo Carvalho de Melo
2002-04-21 15:35 ` Jeff Garzik
2002-04-20 17:09 ` Daniel Phillips
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=20020422164728.H20999@havoc.gtf.org \
--to=garzik@havoc.gtf.org \
--cc=dean-list-linux-kernel@arctic.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lm@bitmover.com \
--cc=phillips@bonn-fries.net \
/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®