From: John Goerzen <jgoerzen@complete.org>
To: linux-kernel@vger.kernel.org
Cc: linux-usb-devel@lists.sourceforge.net
Subject: Re: [BK PATCH] USB changes for 2.5.66
Date: Sat, 29 Mar 2003 08:33:59 -0600 [thread overview]
Message-ID: <87llyyfdig.fsf@complete.org> (raw)
In-Reply-To: Pine.LNX.4.44.0303261029220.15530-100000@home.transmeta.com
Linus Torvalds <torvalds@transmeta.com> writes:
> In other words: _despite_ your luddite ways you actually have more
> information available to you than you would have had without BK.
Not everyone that doesn't use BitKeeper is a luddite. For instance,
Ben Collins has been explicitly prevented from using it simply because
he happens to work on Subversion. His only option is to shell out
thousands for the commercial version. It would serve everyone well to
remember that a minority of contributors to this list have the
financial resources to work around the onerous licensing terms of BK.
next prev parent reply other threads:[~2003-03-29 14:23 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-03-26 0:54 [BK PATCH] USB changes for 2.5.66 Greg KH
2003-03-26 18:17 ` Bill Davidsen
2003-03-26 18:34 ` Linus Torvalds
2003-03-26 20:22 ` [linux-usb-devel] " Alan Cox
2003-03-26 20:42 ` Thomas Molina
2003-03-27 22:48 ` Bill Davidsen
2003-03-29 14:33 ` John Goerzen [this message]
2003-03-26 18:35 ` Greg KH
2003-03-26 20:02 ` Alan Cox
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=87llyyfdig.fsf@complete.org \
--to=jgoerzen@complete.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb-devel@lists.sourceforge.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