From: Eli Zaretskii <eliz@gnu.org>
To: wsw0108@qq.com
Cc: emacs-devel@gnu.org
Subject: Re: branch emacs-28 build broken on MinGW64 with gcc 11
Date: Tue, 23 Nov 2021 16:47:15 +0200 [thread overview]
Message-ID: <83sfvnnd3g.fsf@gnu.org> (raw)
In-Reply-To: <tencent_986B6BF1E7FEA506073AD3DC63FFFD61490A@qq.com> (wsw0108@qq.com)
> From: wsw0108@qq.com
> Date: Tue, 23 Nov 2021 22:42:13 +0800
>
> Sorry, it's my mistake.
>
> After run 'git clean -fdx', the building process can continue without errors.
Ok, thanks for telling us.
prev parent reply other threads:[~2021-11-23 14:47 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-23 12:19 branch emacs-28 build broken on MinGW64 with gcc 11 wsw0108
2021-11-23 13:07 ` Eli Zaretskii
2021-11-23 14:42 ` wsw0108
2021-11-23 14:47 ` Eli Zaretskii [this message]
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=83sfvnnd3g.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=wsw0108@qq.com \
/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).