From: Chris Snook <csnook@redhat.com>
To: devzero@web.de
Cc: linux-kernel@vger.kernel.org
Subject: Re: how much license information inside the kernel ?
Date: Thu, 30 Oct 2008 14:47:07 -0400 [thread overview]
Message-ID: <490A012B.90305@redhat.com> (raw)
In-Reply-To: <488434293@web.de>
devzero@web.de wrote:
> 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.
It may be 3.5 MB uncompressed, but disk space is cheap, and repeated
strings compress extremely well to save bandwidth. If you work with the
kernel source enough for this to be an issue, you should use git.
You'll download these license headers once, and never again unless the
copyright info gets changed by a patch. From a technical perspective,
the problem isn't nearly as bad as it looks, and it keeps the lawyers
happy, so it's really not worth messing with. There's plenty of
lower-hanging fruit in unifying drivers for similar hardware, unifying
32-bit and 64-bit architectures, and other things that make the code
more maintainable.
-- Chris
next prev parent reply other threads:[~2008-10-30 18:48 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 10:54 how much license information inside the kernel ? devzero
2008-10-30 14:24 ` Jörn Engel
2008-10-30 18:47 ` Chris Snook [this message]
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=490A012B.90305@redhat.com \
--to=csnook@redhat.com \
--cc=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