From: Eli Zaretskii <eliz@gnu.org>
To: Ken Brown <kbrown@cornell.edu>
Cc: kzhr@d1.dion.ne.jp, 74312@debbugs.gnu.org
Subject: bug#74312: 31.0.50; Cygw32 build break
Date: Mon, 11 Nov 2024 22:13:06 +0200 [thread overview]
Message-ID: <86wmh9il65.fsf@gnu.org> (raw)
In-Reply-To: <0f292392-7a84-4427-a9ed-9a4dc4014a85@cornell.edu> (message from Ken Brown on Mon, 11 Nov 2024 13:08:13 -0500)
> Date: Mon, 11 Nov 2024 13:08:13 -0500
> Cc: 74312@debbugs.gnu.org
> From: Ken Brown <kbrown@cornell.edu>
>
> On 11/11/2024 11:07 AM, Eli Zaretskii wrote:
> >> Date: Mon, 11 Nov 2024 23:51:33 +0900
> >> From: Kazuhiro Ito <kzhr@d1.dion.ne.jp>
> >>
> >> Cygw32 build fails on master
> >
> > Thanks, I've tried to fix it, please see if there are other problems.
> > And when it does build, please try the drag-n-drop feature, both with
> > dropping files and with dropping text on Emacs.
> >
> > (I repeatedly asked Ken to test these changes with the Cygwin build,
> > but I guess he didn't yet have time. So it's small wonder that the
> > master branch fails to build on Cygwin.)
>
> I'm sorry, but I somehow missed your requests. I'll try to look at this
> within the next few days if Kazuhiro doesn't beat me to it.
Thanks, much appreciated.
next prev parent reply other threads:[~2024-11-11 20:13 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-11 14:51 bug#74312: 31.0.50; Cygw32 build break Kazuhiro Ito
2024-11-11 16:07 ` Eli Zaretskii
2024-11-11 18:08 ` Ken Brown
2024-11-11 20:13 ` Eli Zaretskii [this message]
2024-11-11 22:50 ` Ken Brown
2024-11-12 12:42 ` Eli Zaretskii
2024-11-12 16:14 ` Kazuhiro Ito
2024-11-12 16:47 ` Eli Zaretskii
2024-11-13 10:59 ` Kazuhiro Ito
2024-11-13 12:33 ` Cecilio Pardo
2024-11-13 15:55 ` Kazuhiro Ito
2024-11-14 8:55 ` Cecilio Pardo
2024-11-14 9:39 ` Eli Zaretskii
2024-11-14 10:05 ` Cecilio Pardo
2024-11-14 15:00 ` Kazuhiro Ito
2024-11-14 16:07 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=86wmh9il65.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74312@debbugs.gnu.org \
--cc=kbrown@cornell.edu \
--cc=kzhr@d1.dion.ne.jp \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.