From: vsnsdualce@memeware.net
To: Raul Miller <rauldmiller@gmail.com>
Cc: visionsofalice@redchan.it, freebsd-women@freebsd.org,
freebsd-chat@freebsd.org,
OpenBSD general usage list <misc@openbsd.org>,
owner-misc@openbsd.org, linux-kernel@vger.kernel.org
Subject: Why is no one discussing this anymore?
Date: Thu, 27 Dec 2018 20:30:36 +0000 [thread overview]
Message-ID: <d1a036ae6ecc7614d969e841ee2e9d2f@memeware.net> (raw)
Why is no one discussing this anymore.
It's like you just accepted the "NU UH U WRONG" proclamation from
programmers.
Are you idiots aware that programmers DO NOT KNOW THE LAW simply by
virtue of being "smarts"?
Are you idiots aware that I am a lawyer, I have studied the law, and I
do know more than the programmers on this issue (note: I'm also a
programmer too... but for something useful... like games :) )
Are you idiots aware that Eben Moglen (drafter of the GPLv3 (not 2,
Linux is under 2)) has NOT made good on his pledge to publish a report
on how I'm wrong and let me "correct" him where he got it wrong.
Why do you think that is? That in 2 months nothing.
It's because, as a relative who's worked in the field for many decades
said: he's full of shit.
Anything he publishes would just undermine the stance he's taken.
The license IS recindable at the will of the 1000s of grantors. Any one
of them could shake the tree.
next reply other threads:[~2018-12-27 20:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-27 20:30 vsnsdualce [this message]
2018-12-27 20:48 ` Bon Onlines
2018-12-28 13:57 ` Theodore Y. Ts'o
2018-12-28 17:31 ` Why is no one discussing this anymore? - Attack the messaging rely, not the message! vsnsdualce
[not found] ` <CAKtRYpcHnGW9ftu7UaimH6RejgezeqNZW+rFkEm_GdYdGuXO5A@mail.gmail.com>
2018-12-27 20:57 ` Why is no one discussing this anymore? vsnsdualce
2018-12-27 21:53 ` Bernd Petrovitsch
2018-12-28 16:55 ` vsnsdualce
[not found] ` <20181227235419.27A8ACE1@volny.cz>
2018-12-28 17:22 ` FU: " vsnsdualce
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=d1a036ae6ecc7614d969e841ee2e9d2f@memeware.net \
--to=vsnsdualce@memeware.net \
--cc=freebsd-chat@freebsd.org \
--cc=freebsd-women@freebsd.org \
--cc=linux-kernel@vger.kernel.org \
--cc=misc@openbsd.org \
--cc=owner-misc@openbsd.org \
--cc=rauldmiller@gmail.com \
--cc=visionsofalice@redchan.it \
/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®