From: Eli Zaretskii <eliz@gnu.org>
To: Arash Esbati <arash@gnu.org>
Cc: 55930@debbugs.gnu.org
Subject: bug#55930: 29.0.50; Removing some items from Emacs FAQ for MS Windows
Date: Mon, 13 Jun 2022 16:01:56 +0300 [thread overview]
Message-ID: <83y1y0u37f.fsf@gnu.org> (raw)
In-Reply-To: <86sfo891q0.fsf@gnu.org> (message from Arash Esbati on Mon, 13 Jun 2022 14:39:35 +0200)
> From: Arash Esbati <arash@gnu.org>
> Cc: 55930@debbugs.gnu.org
> Date: Mon, 13 Jun 2022 14:39:35 +0200
>
> > First, I think MinGW64 should nowadays be the main reference, and
> > mingw.org's MinGW just the second choice, specifically for 32-bit
> > builds targeting old Windows versions (which MinGW64 and MSYS2 no
> > longer support).
>
> Thanks for your comments. I presume you mean to make this change
> through the entire FAQ, right? Starting with
>
> 1.2 Which versions of Windows are supported?
>
> and not only in
>
> 11 Other useful ports
>
> ?
Yes.
> > This is IMO too detailed for no good reason. We don't need to "sell"
> > MinGW64. I think we should make it shorter, in the same style as the
> > MinGW/MSYS section.
>
> I don't have any MinGW64/MSYS2 shares ;-) I just wanted to cover the
> aspect that many precompiled binaries of programs are available from
> this project. Maybe I put that note somewhere else.
It's okay to say that many precompiled binaries are available there, I
just don't see a need to affirm that with examples, not in a FAQ.
next prev parent reply other threads:[~2022-06-13 13:01 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-06-12 18:25 bug#55930: 29.0.50; Removing some items from Emacs FAQ for MS Windows Arash Esbati
2022-06-12 18:36 ` Eli Zaretskii
2022-06-13 9:18 ` Arash Esbati
2022-06-13 11:44 ` Eli Zaretskii
2022-06-13 12:39 ` Arash Esbati
2022-06-13 13:01 ` Eli Zaretskii [this message]
2022-06-14 9:23 ` Arash Esbati
2022-06-14 11:59 ` Eli Zaretskii
2022-06-15 8:42 ` Arash Esbati
2022-06-15 16:39 ` Eli Zaretskii
2022-06-15 19:44 ` Arash Esbati
2022-06-16 7:20 ` Eli Zaretskii
2022-06-13 23:46 ` Jim Porter
2022-06-14 9:36 ` 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=83y1y0u37f.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55930@debbugs.gnu.org \
--cc=arash@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).