From: devzero@web.de
To: "Jörn Engel" <joern@logfs.org>
Cc: linux-kernel@vger.kernel.org
Subject: Re: how much license information inside the kernel ?
Date: Thu, 30 Oct 2008 17:12:02 +0100 [thread overview]
Message-ID: <488915452@web.de> (raw)
> On Thu, 30 October 2008 11:54:57 +0100, devzero@web.de wrote:
> >
> > 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.
>
> Scary, isn't it?
iŽm not really scared, but it`s a really impressing amount. :)
> One of the problems is that corporate lawyers require the full GPL
> preample in any source file. As a result, a lot of developers inside
> companies cannot publish code without it. Whether that makes any sense
> is anyone's guess. But it doesn't cause much harm either, so better
> leave the bloat where it is.
i feared something like that.
so, if it`s not just a common bad habit to add those lines again and again
but something being forced by lawyers - it would indeed not being worth
the effort to adress this, as you would need to review and discuss every
single file containing those lines....
thanks for feedback
roland
__________________________________________________________________
"Run, Fatboy, Run" sowie "Rails & Ties" kostenlos anschauen!
Blockbuster-Gutscheine sichern unter http://www.blockbuster.web.de
next reply other threads:[~2008-10-30 16:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-10-30 16:12 devzero [this message]
[not found] <bsDqj-4Tl-49@gated-at.bofh.it>
[not found] ` <btOjA-7Sx-9@gated-at.bofh.it>
2008-11-03 21:37 ` how much license information inside the kernel ? Bodo Eggert
-- strict thread matches above, loose matches on Subject: below --
2008-10-30 19:02 devzero
2008-10-30 10:54 devzero
2008-10-30 14:24 ` Jörn Engel
2008-10-30 18:47 ` Chris Snook
2008-11-02 16:39 ` Pavel Machek
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=488915452@web.de \
--to=devzero@web.de \
--cc=joern@logfs.org \
--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