From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: New emacs maintainer for cygwin
Date: Fri, 15 May 2009 10:35:24 -0400 [thread overview]
Message-ID: <4A0D7DAC.7060302@cornell.edu> (raw)
In-Reply-To: <83ljoyqwmn.fsf@gnu.org>
On 5/15/2009 10:16 AM, Eli Zaretskii wrote:
> Maybe you could look at Cygwin-related bugs filed with the Emacs
> bug-tracker
>
> http://emacsbugs.donarmstrong.com/emacs
>
> and see which ones of them could be fixed before the release.
I'm on my way out of town for a few days, but I'll take a look when I
get back. As you know from previous correspondence, I'm not a
programmer, and I have no debugging experience. But I'll do my best.
> There are also a few Cygwin-related problems in etc/PROBLEMS.
This is way out of date. For example, the information about which gcc
versions are needed is wrong. I'll take a closer look and submit a
patch. If there are any remaining problems, I'll see what I can do.
> The latest pretest version is 23.0.92, to be followed by 23.0.94 in a
> few days.
You meant to say the latest pretest is 23.0.93. I built that as soon as
it came out and have been using it since then, just to make sure there
were no regressions from 23.0.92. I'll also test 23.0.94 and any future
pretests. My reason for using 23.0.92 for the "official" cygwin package
was that I had built it a month ago and knew that it worked well (at
least for me), so I thought I should just stick with that.
Ken
P.S. I subscribe to the emacs-devel list so that I can keep up with
what's going on. Are there any other lists I should watch? I'm not
interested in being inundated with a lot of email, but I do want to know
about it when cygwin issues arise.
next prev parent reply other threads:[~2009-05-15 14:35 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-15 13:41 New emacs maintainer for cygwin Ken Brown
2009-05-15 14:16 ` Eli Zaretskii
2009-05-15 14:35 ` Ken Brown [this message]
2009-05-15 14:42 ` Lennart Borgman
2009-05-15 14:55 ` Chong Yidong
2009-05-17 4:01 ` Stefan Monnier
2009-05-20 0:21 ` Ken Brown
2009-05-20 2:14 ` Stefan Monnier
2009-05-20 2:39 ` Ken Brown
2009-05-20 15:22 ` Stefan Monnier
2009-05-20 17:37 ` Ken Brown
-- strict thread matches above, loose matches on Subject: below --
2009-05-20 8:05 Angelo Graziosi
2009-05-20 12:30 ` Ken Brown
2009-05-20 12:46 ` Angelo Graziosi
2009-05-20 22:19 Angelo Graziosi
2009-05-20 22:39 ` Ken Brown
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=4A0D7DAC.7060302@cornell.edu \
--to=kbrown@cornell.edu \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).