all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: storm@cua.dk (Kim F. Storm)
Cc: emacs-devel@gnu.org
Subject: Re: Suggestion: remove s/sco[45].h etc.
Date: 21 Nov 2003 12:59:11 +0100	[thread overview]
Message-ID: <m3d6bmaq5s.fsf@kfs-l.imdomain.dk> (raw)
In-Reply-To: <87brr6tvk6.fsf@offby1.atm01.sea.blarg.net>

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.

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.

> 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.

-- 
Kim F. Storm <storm@cua.dk> http://www.cua.dk

  reply	other threads:[~2003-11-21 11:59 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 [this message]
2003-11-21 13:05     ` David Kastrup
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

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

  git send-email \
    --in-reply-to=m3d6bmaq5s.fsf@kfs-l.imdomain.dk \
    --to=storm@cua.dk \
    --cc=emacs-devel@gnu.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.
Code repositories for project(s) associated with this external index

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

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.