From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: rms@gnu.org, emacs-devel@gnu.org
Subject: Re: Support for MS-Windows build of Emacs
Date: Tue, 30 Jul 2024 19:03:37 +0300 [thread overview]
Message-ID: <86v80myihy.fsf@gnu.org> (raw)
In-Reply-To: <m2y15j3qbf.fsf@macmutant.fritz.box> (message from Arash Esbati on Tue, 30 Jul 2024 16:30:28 +0200)
> From: Arash Esbati <arash@gnu.org>
> Cc: eliz@gnu.org, emacs-devel@gnu.org
> Date: Tue, 30 Jul 2024 16:30:28 +0200
>
> Richard Stallman <rms@gnu.org> writes:
>
> > However, as long as people keep wanting to use Emacs on those nonfree
> > systems, I hope some of them will step forward and support Emacs there.
> >
> > Is there a way we can encourage them to?
>
> I suggest to look back and ask what was the process until now that the
> project is facing this situation.
IMO, there's nothing to look at. We used to have people here who were
both Emacs developers and used Emacs on Windows enough to care about
the port. They have simply left, for reasons that AFAIR have nothing
to do with us or the way we do things here.
next prev parent reply other threads:[~2024-07-30 16:03 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-24 20:16 Warnings during building the current master on Win10 with MSYS2/MinGW64 Arash Esbati
2024-07-25 5:52 ` Support for MS-Windows build of Emacs (was: Warnings during building the current master on Win10 with MSYS2/MinGW64) Eli Zaretskii
2024-07-25 11:03 ` Support for MS-Windows build of Emacs Arash Esbati
2024-07-25 11:38 ` Po Lu
2024-07-28 2:58 ` Richard Stallman
2024-07-30 14:30 ` Arash Esbati
2024-07-30 16:03 ` Eli Zaretskii [this message]
2024-07-30 16:34 ` Juergen Fenn
2024-07-29 14:13 ` Support for MS-Windows build of Emacs (was: Warnings during building the current master on Win10 with MSYS2/MinGW64) Tom Davey
2024-07-25 5:56 ` Warnings during building the current master on Win10 with MSYS2/MinGW64 Eli Zaretskii
2024-07-25 6:49 ` Collin Funk
2024-07-25 11:11 ` Arash Esbati
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=86v80myihy.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=arash@gnu.org \
--cc=emacs-devel@gnu.org \
--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).