public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: devzero@web.de
To: linux-kernel@vger.kernel.org
Subject: how much license information inside the kernel ?
Date: Thu, 30 Oct 2008 11:54:57 +0100	[thread overview]
Message-ID: <488434293@web.de> (raw)

hi, 

i found that there is a LOT of repeating licensing information in the kernel.

for me, 

find ./linux-2.6.27 -type f -exec cat {} \; |egrep "free software|GNU General Public License|Free Software Foundation|version 2 of the License|distributed in the hope|WITHOUT ANY WARRANTY|FITNESS FOR A PARTICULAR"

gives a file sized ~3.5M

That`s more than 1% of the kernel source.

What about the idea to shorten that licening information to a minimum , e.g. by shrinking that to a single, catchy line ,  linking to a special licensing file like COPYING or linking to the FSF website ?

please no flames, i know this idea could be pure dynamite for some people - but i thought 3.5M is worth this mail.

regards
roland

ps:
i`m not sure if that has been discussed already, but i didn`t find that in the archive. please ignore, otherwise.
________________________________________________________________________
n 5 Schritten zur eigenen Homepage. Jetzt Domain sichern und gestalten! 
Nur 3,99 EUR/Monat! http://www.maildomain.web.de/?mc=021114


             reply	other threads:[~2008-10-30 10:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-10-30 10:54 devzero [this message]
2008-10-30 14:24 ` how much license information inside the kernel ? Jörn Engel
2008-10-30 18:47 ` Chris Snook
2008-11-02 16:39 ` Pavel Machek
  -- strict thread matches above, loose matches on Subject: below --
2008-10-30 16:12 devzero
2008-10-30 19:02 devzero
     [not found] <bsDqj-4Tl-49@gated-at.bofh.it>
     [not found] ` <btOjA-7Sx-9@gated-at.bofh.it>
2008-11-03 21:37   ` Bodo Eggert

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=488434293@web.de \
    --to=devzero@web.de \
    --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