From: Corwin Brust <corwin@bru.st>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Ken Brown <kbrown@cornell.edu>, Po Lu <luangruo@yahoo.com>,
Stefan Kangas <stefankangas@gmail.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: Windows 9X without KernelEx
Date: Tue, 25 Jun 2024 20:20:55 +0100 [thread overview]
Message-ID: <CAJf-WoS-d8=SZxSqfZRjMZrRDRrhV0DpcgswbOKq9Yh1O+38Tw@mail.gmail.com> (raw)
In-Reply-To: <86a5jbcbt9.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 696 bytes --]
On Mon, Jun 24, 2024, 03:30 Eli Zaretskii <eliz@gnu.org> wrote:
> > Date: Sun, 23 Jun 2024 16:25:13 -0400
> > Cc: stefankangas@gmail.com, emacs-devel@gnu.org
> > From: Ken Brown <kbrown@cornell.edu>
> >
> > On 6/23/2024 5:16 AM, Eli Zaretskii wrote:
> > >> From: Po Lu <luangruo@yahoo.com>
>
> > >> Therefore, would you please arrange that this message fall on the
> right
> > >> ears for the contents of the branch to be tested in this
> configuration?
> > >
> > > That would be Ken and Corwin, I believe.
> >
> > Builds fine on Cygwin.
>
> Thanks.
>
FTR I have been following this thread but am traveling internationally
without any Windows PC. I look forward to trying out the branch.
>
>
[-- Attachment #2: Type: text/html, Size: 1594 bytes --]
next prev parent reply other threads:[~2024-06-25 19:20 UTC|newest]
Thread overview: 50+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <875xub8sn8.fsf.ref@yahoo.com>
2024-06-14 15:12 ` Windows 9X without KernelEx Po Lu via Emacs development discussions.
2024-06-14 15:26 ` Eli Zaretskii
2024-06-14 15:37 ` Po Lu
2024-06-14 16:06 ` Eli Zaretskii
2024-06-15 1:42 ` Po Lu
2024-06-15 2:42 ` Po Lu
2024-06-15 6:58 ` Eli Zaretskii
2024-06-15 7:12 ` Po Lu
2024-06-15 7:37 ` Eli Zaretskii
2024-06-15 7:45 ` Po Lu
2024-06-15 7:50 ` Eli Zaretskii
2024-06-15 9:39 ` Po Lu
2024-06-15 12:38 ` Eli Zaretskii
2024-06-15 13:10 ` Po Lu
2024-06-15 13:22 ` Eli Zaretskii
2024-06-15 13:31 ` Po Lu
2024-06-15 4:07 ` Stefan Kangas
2024-06-15 4:14 ` Po Lu
2024-06-15 4:45 ` Po Lu
2024-06-15 7:07 ` Eli Zaretskii
2024-06-15 7:22 ` Po Lu
2024-06-15 7:42 ` Eli Zaretskii
2024-06-15 9:35 ` Po Lu via Emacs development discussions.
2024-06-15 13:52 ` Eli Zaretskii
2024-06-15 14:18 ` Po Lu
2024-06-15 14:55 ` Eli Zaretskii
2024-06-15 15:15 ` Po Lu
2024-06-15 16:01 ` Eli Zaretskii
2024-06-16 2:01 ` Po Lu
2024-06-16 5:36 ` Eli Zaretskii
2024-06-16 5:50 ` Eli Zaretskii
2024-06-16 6:53 ` Po Lu
2024-06-16 11:34 ` Po Lu
2024-06-16 12:21 ` Eli Zaretskii
2024-06-23 8:35 ` Po Lu
2024-06-23 9:16 ` Eli Zaretskii
2024-06-23 20:25 ` Ken Brown
2024-06-24 2:30 ` Eli Zaretskii
2024-06-24 3:53 ` Po Lu
2024-06-25 19:20 ` Corwin Brust [this message]
2024-06-24 17:17 ` Ken Brown
2024-06-24 22:11 ` Ken Brown
2024-06-25 22:41 ` Ken Brown
2024-06-27 1:59 ` Po Lu
2024-06-27 13:18 ` Ken Brown
2024-06-27 13:42 ` Po Lu
2024-06-27 13:47 ` Po Lu
2024-06-27 14:52 ` Ken Brown
2024-06-30 2:07 ` Po Lu
2024-06-15 7:01 ` 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
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='CAJf-WoS-d8=SZxSqfZRjMZrRDRrhV0DpcgswbOKq9Yh1O+38Tw@mail.gmail.com' \
--to=corwin@bru.st \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=kbrown@cornell.edu \
--cc=luangruo@yahoo.com \
--cc=stefankangas@gmail.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).