From: Dana Lacoste <dana.lacoste@peregrine.com> To: linux-kernel@vger.kernel.org Subject: Can we keep it toned down a bit in here? Date: 25 Jul 2003 11:15:19 -0400 [thread overview] Message-ID: <1059146119.968.74.camel@dlacoste.ottawa.loran.com> (raw) OK, as entertaining as it has been (though I would've preferred more posts from Al Viro : he has a great way with words :) can we all agree that BK/GPL/OSL issues should go somewhere else? Like maybe an advocacy list instead of a development list? I've seen the following debated endlessly (with the rhetoric turned way up these past few weeks) : - RMS is a cheat trying to steal copyrights from everyone - RMS is a saviour trying to save the world - The GPL is a virus that is not legally enforcable and tries to promote RMS's political agenda - The GPL is the only thing keeping Linux free - BK is spawned from the same pits of hell that Saddam Hussein came from (south park is a wonderful learning tool) - BK is a great piece of software that solves all of our problems and allows Larry to make a (legal) living Can we just agree that the Linus' acts are answer enough? - The GPL isn't perfect, thus the restrictions in the kernel source (specific versions of the GPL only) - BK isn't perfect, but it is free and solves a lot of problems in developing the Linux kernel. Advocating a program and using a program aren't the same thing after all! - RMS is fighting the good fight, even if he is a bit more extreme than many of us would prefer. Better Gnu/Linux than MS/Linux! Stop the trolling! Make code not war! Dana Lacoste Ottawa, Canada
next reply other threads:[~2003-07-25 15:00 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2003-07-25 15:15 Dana Lacoste [this message] 2003-07-25 15:56 ` Martin List-Petersen 2003-07-25 16:41 ` Olaf Dietsche 2003-07-25 17:12 ` vlad
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=1059146119.968.74.camel@dlacoste.ottawa.loran.com \ --to=dana.lacoste@peregrine.com \ --cc=linux-kernel@vger.kernel.org \ --subject='Re: Can we keep it toned down a bit in here?' \ /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
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for NNTP newsgroup(s).