git@vger.kernel.org mailing list mirror (one of many)
 help / color / mirror / code / Atom feed
From: Linus Torvalds <torvalds@linux-foundation.org>
To: "Alfred M. Szmidt" <ams@gnu.org>
Cc: Johannes.Schindelin@gmx.de, git@vger.kernel.org
Subject: Re: [PATCH] Cast things properly to handle >2G files.
Date: Wed, 17 Jun 2009 15:48:44 -0700 (PDT)	[thread overview]
Message-ID: <alpine.LFD.2.01.0906171543510.16802@localhost.localdomain> (raw)
In-Reply-To: <E1MH3bD-0004fq-07@fencepost.gnu.org>



On Wed, 17 Jun 2009, Alfred M. Szmidt wrote:
>    The DCO, in contrast, is a paragon of simplicity and clarity, and
>    doesn't ask you to sign away any rights.
> 
> You are misinformed.  The copyright assignments from the FSF explictly
> state that the code will always be free software, and they grant back
> all rights to the code you assigned to them.

Blah. They define the term "free software" too, so that doesn't make any 
difference. They can relicense it any crazy way they want, as shown by the 
whole annoying GPLv3 idiocy. It doesn't matter one whit whether you agree 
with them or not.

And isn't it "nice" of them to not require exclusive ownership? Gag. And 
what a bunch of hypocritical people they are too - because they'll happily 
take code from other people without any copyright assignment what-so-ever 
when they feel like it (case in point: Hurd took drivers and filesystems 
from Linux, and I can pretty much guarantee that they didn't have 
copyright assignments for any of it - but hey, rules are rules only when 
they apply to _other_ people, right?)

And you didn't face the actual issue: the papers the FSF makes you sign 
are _way_ less obvious than the DCO is.

		Linus

  reply	other threads:[~2009-06-17 22:48 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-14 20:03 [PATCH] Cast things properly to handle >2G files Alfred M. Szmidt
2009-06-14 20:17 ` Johannes Schindelin
2009-06-15  2:43   ` Nicolas Pitre
2009-06-15  3:39   ` Alfred M. Szmidt
2009-06-15  4:06     ` Junio C Hamano
2009-06-15  8:45       ` Johannes Schindelin
2009-06-15  4:25     ` Linus Torvalds
2009-06-17 22:27       ` Alfred M. Szmidt
2009-06-17 22:48         ` Linus Torvalds [this message]
2009-06-17 22:27       ` Alfred M. Szmidt
2009-06-17 22:45         ` Linus Torvalds
2009-06-17 23:16           ` Junio C Hamano
2009-06-18  0:22           ` Fix big left-shifts of unsigned char Linus Torvalds
2009-06-18  8:12             ` Johannes Schindelin
2009-06-18  8:21               ` Junio C Hamano
2009-06-18 16:08               ` Linus Torvalds
2009-06-18 16:45                 ` Johannes Schindelin
2009-06-18 17:15                   ` Linus Torvalds
2009-06-18 17:28                     ` Fix various sparse warnings in the git source code Linus Torvalds
2009-06-18 17:45                       ` Matthieu Moy
2009-06-18 17:52                         ` Linus Torvalds
2009-06-18 21:48                       ` Linus Torvalds
2009-06-17 22:51         ` [PATCH] Cast things properly to handle >2G files Linus Torvalds

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

  List information: http://vger.kernel.org/majordomo-info.html

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=alpine.LFD.2.01.0906171543510.16802@localhost.localdomain \
    --to=torvalds@linux-foundation.org \
    --cc=Johannes.Schindelin@gmx.de \
    --cc=ams@gnu.org \
    --cc=git@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.
Code repositories for project(s) associated with this public inbox

	https://80x24.org/mirrors/git.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).