From: Ken Brown <kbrown@cornell.edu>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 10398@debbugs.gnu.org, larsi@gnus.org
Subject: bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days
Date: Wed, 11 Apr 2012 08:35:02 -0400 [thread overview]
Message-ID: <4F857A76.9040208@cornell.edu> (raw)
In-Reply-To: <83d37e5wgv.fsf@gnu.org>
On 4/11/2012 7:39 AM, Eli Zaretskii wrote:
>> Date: Wed, 11 Apr 2012 07:15:46 -0400
>> From: Ken Brown<kbrown@cornell.edu>
>> CC: Lars Magne Ingebrigtsen<larsi@gnus.org>, dancol@dancol.org,
>> 10398@debbugs.gnu.org, Chong Yidong<cyd@stupidchicken.com>
>>
>> I don't think we should make an effort to support Cygwin versions
>> earlier than 1.7. Cygwin 1.5 is no longer supported by Cygwin, so I
>> don't see a reason for emacs to try to support it. I suspect there
>> have been many emacs changes that are not compatible with Cygwin
>> 1.5.
>
> Fair enough, but then perhaps the configure script should at least
> warn, or maybe even refuse to continue, if it sees an older version?
A warning would be fine, but I would suggest waiting until someone
reports an actual problem. My guess is that no one running Cygwin 1.5
will ever try to build the emacs trunk. But if someone does try and
runs into problems, we can take the appropriate action. If you
disagree, I have no objection to inserting a warning now.
Ken
next prev parent reply other threads:[~2012-04-11 12:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-29 14:06 bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days Daniel Colascione
2012-04-10 23:26 ` Lars Magne Ingebrigtsen
2012-04-11 6:47 ` Chong Yidong
2012-04-11 6:58 ` Eli Zaretskii
2012-04-11 11:15 ` Ken Brown
2012-04-11 11:39 ` Eli Zaretskii
2012-04-11 12:35 ` Ken Brown [this message]
2012-04-11 19:26 ` Eli Zaretskii
2012-04-12 2:51 ` Ken Brown
2012-04-12 4:53 ` Glenn Morris
2012-04-12 6:00 ` Eli Zaretskii
2012-04-12 7:40 ` Andreas Schwab
2012-04-12 12:21 ` Ken Brown
2012-04-11 17:48 ` Drew Adams
2012-04-11 19:37 ` Ken Brown
2012-04-11 20:04 ` Drew Adams
2012-04-11 11:44 ` Lars Magne Ingebrigtsen
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=4F857A76.9040208@cornell.edu \
--to=kbrown@cornell.edu \
--cc=10398@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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).