unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
Cc: Eric Hanchrow <offby1@blarg.net>, emacs-devel@gnu.org
Subject: Re: Suggestion: remove s/sco[45].h etc.
Date: 21 Nov 2003 14:05:20 +0100	[thread overview]
Message-ID: <x5znepeusu.fsf@lola.goethe.zz> (raw)
In-Reply-To: <m3d6bmaq5s.fsf@kfs-l.imdomain.dk>

storm@cua.dk (Kim F. Storm) writes:

> Eric Hanchrow <offby1@blarg.net> writes:
> 
> > I agree with Kastrup and Lemon -- if SCO is worse than other
> > developers of proprietary systems, it is only in degree, not in
> > kind,
> 
> I don't think any of the other developers have gone as far as
> questioned the legality of the GPL -- even claiming it to be
> non-constitutional.

Oh come on.  Microsoft has called it against the values of the
American constitution or society or some stuff like that.
Repeatedly.  And I can't count the number of times communism has been
brought up by them.

They might not have gone all the way that the current suicide mission
of SCO permits: those at the helm can't lose: all their hype and talk
is putting them into the headlines and thus is driving the stock
market value up artificially and the key players will have sold out
long before the company crashes.

> I agree that M$ is trying its best to bad-mouth the free and open
> software movements.  However, (except for the recent "dontation" to
> SCO) I don't think they have gone as far as SCO.

Well, they are not on a Kamikaze spree, that's all.

> > and Emacs already supports lots of non-free systems.  I doubt that
> > denying SCO customers the latest Emacs will further the cause of
> > software freedom.
> 
> I agree, it is a concern that my proposed move isn't friendly to SCO
> users, nor does it promote the use of free software on SCO
> platforms.
> 
> The reason for my question is that there have been recent bug
> reports (admittedly with fixes) for SCO-specific problems.
> 
> Personally, I don't want to spend any time on fixing such problems,
> but others may feel differently.

It is fine with me if you don't feel like spending any time to fix
such problems.  In fact, I would not either.  But you were proposing
instead spending time on sabotaging the usability of Emacs on SCO
platforms completely.  And I object to that.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum

  reply	other threads:[~2003-11-21 13:05 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-11-20 23:26 Suggestion: remove s/sco[45].h etc Kim F. Storm
2003-11-20 23:36 ` David Kastrup
2003-11-20 23:47 ` Ted Lemon
2003-11-21  0:27 ` Eric Hanchrow
2003-11-21 11:59   ` Kim F. Storm
2003-11-21 13:05     ` David Kastrup [this message]
2003-11-22  0:09       ` Kim F. Storm
2003-11-22 21:19 ` Richard Stallman

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=x5znepeusu.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=offby1@blarg.net \
    /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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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 read-only IMAP folder(s) and NNTP newsgroup(s).