From: Eli Zaretskii <eliz@gnu.org>
To: "Perry E. Metzger" <perry@piermont.com>
Cc: eggert@cs.ucla.edu, emacs-devel@gnu.org, rms@gnu.org,
phillip.lord@russet.org.uk
Subject: Re: Windows emacs-25.1 i686 vs x86_64?
Date: Mon, 07 Nov 2016 21:29:03 +0200 [thread overview]
Message-ID: <83r36ngkcg.fsf@gnu.org> (raw)
In-Reply-To: <20161107140228.0a60be57@jabberwock.cb.piermont.com> (perry@piermont.com)
> Date: Mon, 7 Nov 2016 14:02:28 -0500
> From: "Perry E. Metzger" <perry@piermont.com>
> Cc: Paul Eggert <eggert@cs.ucla.edu>, phillip.lord@russet.org.uk,
> rms@gnu.org, emacs-devel@gnu.org
>
> I'm somewhat surprised that we're discussing support for a proprietary
> OS that has been off vendor extended support for over a decade and
> which no one uses any more.
We aren't. "Discussing support" would be talking about some code that
needs to be written or rewritten or changed in support of that OS.
Nothing of the sort is on the table; the code is already written, was
written long ago, actually, and no one suggested to work on it, let
alone improve it.
What we are doing is we are bikeshedding about a short paragraph of
text that I added back to a README, that's all. It's a mouse that
gave birth to a mountain. I guess we have nothing more important to
do with our time.
next prev parent reply other threads:[~2016-11-07 19:29 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <6e2cffe5-942b-48d4-9ed5-ef39803bcd30@googlegroups.com>
[not found] ` <b361e3a3-849e-486a-b758-64316c0efea5@googlegroups.com>
[not found] ` <87mvhgsf21.fsf@russet.org.uk>
[not found] ` <8360o4monq.fsf@gnu.org>
[not found] ` <87vaw4gq0j.fsf@russet.org.uk>
[not found] ` <83oa1vlnkk.fsf@gnu.org>
[not found] ` <87d1iba6od.fsf@russet.org.uk>
2016-11-05 8:16 ` Windows emacs-25.1 i686 vs x86_64? Eli Zaretskii
2016-11-05 22:26 ` Phillip Lord
2016-11-06 3:43 ` Eli Zaretskii
2016-11-06 8:10 ` Paul Eggert
2016-11-06 15:48 ` Eli Zaretskii
2016-11-06 16:13 ` Óscar Fuentes
2016-11-06 16:43 ` Eli Zaretskii
2016-11-06 17:01 ` Óscar Fuentes
2016-11-06 17:24 ` Eli Zaretskii
2016-11-06 18:26 ` Óscar Fuentes
2016-11-06 18:42 ` Eli Zaretskii
2016-11-06 19:17 ` Eli Zaretskii
2016-11-06 20:15 ` Óscar Fuentes
2016-11-07 14:40 ` Richard Stallman
2016-11-07 15:16 ` Phillip Lord
2016-11-08 13:53 ` Richard Stallman
2016-11-06 16:51 ` Stefan Monnier
2016-11-06 18:50 ` John Wiegley
2016-11-07 14:42 ` Richard Stallman
2016-11-06 21:54 ` Paul Eggert
2016-11-06 21:57 ` Daniel Colascione
2016-11-07 14:43 ` Richard Stallman
2016-11-07 15:15 ` Daniel Colascione
2016-11-07 15:26 ` Phillip Lord
2016-11-08 13:53 ` Richard Stallman
2016-11-08 14:52 ` Phillip Lord
2016-11-08 15:31 ` Eli Zaretskii
2016-11-09 16:50 ` Phillip Lord
2016-11-09 17:15 ` Eli Zaretskii
2016-11-09 17:18 ` Stefan Monnier
2016-11-10 15:19 ` Phillip Lord
2016-11-09 7:00 ` martin rudalics
2016-11-15 10:26 ` Phillip Lord
2016-11-07 16:34 ` Paul Eggert
2016-11-07 18:07 ` Eli Zaretskii
2016-11-07 19:02 ` Perry E. Metzger
2016-11-07 19:29 ` Eli Zaretskii [this message]
2016-11-07 21:54 ` Phillip Lord
2016-11-07 19:39 ` Stefan Monnier
2016-11-07 20:02 ` Perry E. Metzger
2016-11-07 20:10 ` Stefan Monnier
2016-11-07 20:22 ` Perry E. Metzger
2016-11-07 20:27 ` Eli Zaretskii
2016-11-08 3:48 ` Elias Mårtenson
2016-11-08 15:32 ` Eli Zaretskii
2016-11-07 18:49 ` Perry E. Metzger
2016-11-08 13:55 ` Richard Stallman
2016-11-08 14:34 ` Perry E. Metzger
2016-11-06 21:50 ` Phillip Lord
2016-11-06 4:13 ` Noam Postavsky
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=83r36ngkcg.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=emacs-devel@gnu.org \
--cc=perry@piermont.com \
--cc=phillip.lord@russet.org.uk \
--cc=rms@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).