mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: aconcernedfossdev@airmail.cc
To: linux-kernel@vger.kernel.org
Subject: Some Libre Songs, Including one on GRSecurity's copyright Violation. Step up and listen, unless you can't handle it. BRUV (Bin that knoif)
Date: Thu, 15 Jun 2017 16:39:08 +0000	[thread overview]
Message-ID: <af7138658268314045dd46b8cbfd4860@airmail.cc> (raw)

Some Free/Libre/Opensource Songs for all of you here working on the 
LINUX KERNEL!, Including one on GRSecurity's copyright Violation

This song is about GRSecurity's violation of Linus et al's copyright**:
www.youtube.com/watch?v=CYnhI3wUej8
(A Boat Sails Away 2016 17)


Here's a synthwave song with a kind-of beat:
www.youtube.com/watch?v=RCbeOsqwUEE
(KMS20Beats2017)

Hat Trick Song:
watch?v=Qc37gvAOGRg

This one is like a Roman march
www.youtube.com/watch?v=NsbDGuzXDrA

All are dual licensed GPL v2 and CC-BY-SA 3.0
Author is MikeeUSA
Audacity "source" zips are available at the media project page.

Enjoy, Linux Bros!
Tell ME what you think (TO MY FACE!!!!)

-------

**:
The license grant the Linux Kernel is distributed under disallows the 
imposition of additional terms.
The making of an understanding that the derivative work must not be 
redistributed (lest there be retaliation) is the imposition of an 
additional term.
The communication of this threat is the moment that GRSecurity violates 
the license grant.
Thence-forth modification, making of derivative works, and distribution 
of such is a violation of the Copyright statute.
The concoction of the transparent scheme shows that it is a willful 
violation, one taken in full knowledge by GRSecurity of the intention of 
the original grantor.

             reply	other threads:[~2017-06-15 16:39 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-15 16:39 aconcernedfossdev [this message]
2017-06-15 16:45 ` aconcernedfossdev

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=af7138658268314045dd46b8cbfd4860@airmail.cc \
    --to=aconcernedfossdev@airmail.cc \
    --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

all inboxes | Powered by JetHome®