From: Ken Brown <kbrown@cornell.edu>
To: Drew Adams <drew.adams@oracle.com>
Cc: 10398@debbugs.gnu.org, 'Lars Magne Ingebrigtsen' <larsi@gnus.org>
Subject: bug#10398: [PATCH] Use real vfork under Cygwin: it's fine these days
Date: Wed, 11 Apr 2012 15:37:26 -0400 [thread overview]
Message-ID: <4F85DD76.8060709@cornell.edu> (raw)
In-Reply-To: <04D7A5D8308A49989EC5E1DD5979D761@us.oracle.com>
On 4/11/2012 1:48 PM, Drew Adams wrote:
>> I think it's a good change. And 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.
>
> Dunno what is meant here by "support Cygwin", but FWIW (probably not much) I
> still use Cygwin 1.5. I do so because it seems to work OK for my use cases and
> because I have come across lots of problems reported here and there wrt later
> versions (and Emacs).
>
> (Yes, I know, you can find whatever problems you want on the Internet, real or
> wrong. Still, why upgrade if I don't need to?)
>
> I do not run Emacs inside Cygwin, but I use Cygwin's `grep' and other commands
> from Emacs, and I use Cygwin's bash shell interactively.
The change we're talking about here won't affect you. It's only
relevant to people working in Cygwin and building the Emacs trunk (for
use within Cygwin).
Ken
next prev parent reply other threads:[~2012-04-11 19:37 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
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 [this message]
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=4F85DD76.8060709@cornell.edu \
--to=kbrown@cornell.edu \
--cc=10398@debbugs.gnu.org \
--cc=drew.adams@oracle.com \
--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).