unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: David Kastrup <dak@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: ams@gnu.org, emacs-devel@gnu.org
Subject: Re: Meanness
Date: Sat, 26 Jul 2008 19:01:11 +0200	[thread overview]
Message-ID: <85fxpw1sx4.fsf@lola.goethe.zz> (raw)
In-Reply-To: <usktw4n46.fsf@gnu.org> (Eli Zaretskii's message of "Sat, 26 Jul 2008 19:38:17 +0300")

Eli Zaretskii <eliz@gnu.org> writes:

>> CC: emacs-devel@gnu.org
>> From: "Alfred M. Szmidt" <ams@gnu.org>
>> Date: Sat, 26 Jul 2008 12:16:18 -0400
>> 
>>    We have a common goal here: improving Emacs.  
>> 
>> And the goal of Emacs is to improve the GNU operating system, and not
>> non-free operating systems.
>
> As long as Emacs is not sold to Microsoft nor bundled with it out of
> the box, no one can claim that I'm improving non-free operating
> systems.

Does that mean that you would not work on supporting Bash on Windows
since a Bash port has been sold to Microsoft by Interix and is being
distributed by Microsoft as part of SFU (Services for Unix)?  The same
appears to hold for GNU file and text utilities, and certainly for the
"GNU SDK" including GCC.

But that's missing the point.  Of course free software will also get
used and employed on proprietary systems.  It is one consequence of
their freedom.  The question was whether we should make it _our_ focus,
the focus of the GNU project.  Opinions differ.  But whether this
warrants the Guy Fawkes festival of strawmen burning we have seen in
response, I doubt.

-- 
David Kastrup, Kriemhildstr. 15, 44793 Bochum




  reply	other threads:[~2008-07-26 17:01 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-07-26  8:10 Meanness Alan Mackenzie
2008-07-26 11:49 ` Meanness Alfred M. Szmidt
2008-07-26 11:59   ` Meanness Alan Mackenzie
2008-07-26 12:04     ` Meanness Alfred M. Szmidt
2008-07-26 15:16   ` Meanness Eli Zaretskii
2008-07-26 15:27     ` Meanness Juanma Barranquero
2008-07-26 15:51       ` Meanness David Kastrup
2008-07-26 16:11         ` Meanness Juanma Barranquero
2008-07-26 16:30           ` Meanness David Kastrup
2008-07-26 16:40             ` Meanness Eli Zaretskii
2008-07-26 16:52             ` Meanness Juanma Barranquero
2008-07-26 16:59         ` Meanness Eli Zaretskii
2008-07-26 17:49         ` Meanness Thomas Lord
2008-07-26 17:21           ` Meanness David Kastrup
2008-07-26 17:36             ` Meanness Eli Zaretskii
2008-07-26 18:10               ` Meanness David Kastrup
2008-08-30  2:10             ` Meanness Daniel Colascione
2008-07-26 15:37     ` Meanness David Kastrup
2008-07-26 16:49       ` Meanness Eli Zaretskii
2008-07-26 16:00     ` Meanness Óscar Fuentes
2008-07-26 16:19       ` Meanness David Kastrup
2008-07-26 16:56         ` Meanness Óscar Fuentes
2008-07-27 14:49       ` Meanness Richard M Stallman
2008-07-26 16:16     ` Meanness Alfred M. Szmidt
2008-07-26 16:20       ` Meanness Chong Yidong
2008-07-26 16:37         ` Meanness David Kastrup
2008-07-26 16:38       ` Meanness Eli Zaretskii
2008-07-26 17:01         ` David Kastrup [this message]
2008-07-26 17:22           ` Meanness Eli Zaretskii
2008-07-27 14:49       ` Meanness Richard M Stallman
2008-07-27 14:49     ` Meanness Richard M Stallman
2008-07-26 18:08 ` Meanness Stefan Monnier

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=85fxpw1sx4.fsf@lola.goethe.zz \
    --to=dak@gnu.org \
    --cc=ams@gnu.org \
    --cc=eliz@gnu.org \
    --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 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).