From: Dmitry Gutov <dgutov@yandex.ru>
To: Paul Eggert <eggert@cs.ucla.edu>, Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: Omitting Windows-specific parts from infrastructure changes
Date: Wed, 21 Jan 2015 22:07:02 +0200 [thread overview]
Message-ID: <54C006E6.8060700@yandex.ru> (raw)
In-Reply-To: <54C00076.1020406@cs.ucla.edu>
On 01/21/2015 09:39 PM, Paul Eggert wrote:
> Wow, is this really a threat to block or revert changes to the Emacs
> mainline code, as leverage to force people to do unnecessary drudgework
Regardless of the outcome of this discussion, I hope everyone realizes
that the presence and adequate functioning of Emacs ports to proprietary
operating systems is beneficial to GNU/Linux users as well, since it
increases the size of the ecosystem.
For instance, the maintainer of what currently seems to be the best hope
for a Java editing environment (malabar-mode) uses Windows.
Yours truly has spent quite a bit of time on Windows as well. Had Emacs
port not been available then, I'd probably have ended up not using it at
all in the end.
> to help polish up the MS-Windows code?
It seems to me that the goal is to help keep it up-to-date.
(Sorry for butting in).
next prev parent reply other threads:[~2015-01-21 20:07 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-16 9:54 Omitting Windows-specific parts from infrastructure changes Eli Zaretskii
2015-01-17 3:39 ` Paul Eggert
2015-01-17 8:34 ` Eli Zaretskii
2015-01-18 18:09 ` Paul Eggert
2015-01-18 18:23 ` Eli Zaretskii
2015-01-18 19:25 ` Paul Eggert
2015-01-18 19:50 ` Eli Zaretskii
2015-01-18 20:34 ` Paul Eggert
2015-01-19 16:03 ` Eli Zaretskii
2015-01-19 18:00 ` Paul Eggert
2015-01-19 18:32 ` Eli Zaretskii
2015-01-19 22:14 ` Paul Eggert
2015-01-20 16:32 ` Eli Zaretskii
2015-01-20 21:28 ` Paul Eggert
2015-01-21 15:48 ` Eli Zaretskii
2015-01-21 17:32 ` Paul Eggert
2015-01-21 17:55 ` Eli Zaretskii
2015-01-21 19:39 ` Paul Eggert
2015-01-21 20:07 ` Dmitry Gutov [this message]
2015-01-21 20:38 ` Eli Zaretskii
2015-01-21 20:08 ` David Kastrup
2015-01-21 20:49 ` Eli Zaretskii
2015-01-21 20:57 ` David Kastrup
2015-01-22 3:53 ` Eli Zaretskii
2015-01-21 20:30 ` Eli Zaretskii
2015-01-21 20:49 ` David Kastrup
2015-01-22 3:51 ` Eli Zaretskii
2015-01-22 14:20 ` 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=54C006E6.8060700@yandex.ru \
--to=dgutov@yandex.ru \
--cc=eggert@cs.ucla.edu \
--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).