From: Ray Donnelly <mingw.android@gmail.com>
To: cygwin@cygwin.com
Subject: Re: Bug report: Killing a native process may not actually kill it
Date: Tue, 03 Sep 2019 05:38:00 -0000 [thread overview]
Message-ID: <CAOYw7dsxif5+JpGL+hK91t_owzkgEmY-kRJOP68ignOQXkeaug@mail.gmail.com> (raw)
In-Reply-To: <5d671e60.1c69fb81.eba3d.1ef8@mx.google.com>
On Thu, 29 Aug 2019, 02:38 Steven Penny, <svnpenn@gmail.com> wrote:
> On Wed, 28 Aug 2019 15:57:23, Quanah Gibson-Mount wrote:
> > My original post contained a link to a patch allowing for Cygwin to
> > correctly terminate native Windows processes. I understand it is not
> the
> > position of the Cygwin project to deal with situation, so I think we can
> > just let it drop.
>
> I would like to say that I support this, if it can be done in a reasonable
> way.
>
> Ive been reading this thread carefully, and Ive yet to see anyone comment
> on the
> merits of the patch. Apologies if Ive overlooked it.
>
> To me, the first and only question that matters is "does it solve more
> problems
> than it causes". If the answer is yes, I think the patch should be
> accepted.
> Else I think its unfair to prematurely end the discussion.
>
> Cygwin has a long history of... putting Cygwin first. I dont mean this as a
> negative, although I do disagree with the sentiment. Any compiling is with
> Cygwin target as first class citizen, then native Windows has always been
> an
> afterthought. I think this is why the MinGW survived as long as it did, and
> while the MSYS2 project enjoys the popularity it has today. With MSYS2, the
> "Cygwin" mode is still primary, but you can launch "mingw64.exe" and native
> Windows becomes the default.
>
We can consider the patch at msys2 also if you wish to propose it.
>
> If Cygwin wishes to remain insular in regard to this and other native
> Windows
> issues, thats their choice. It does make development significantly easier I
> assume. However I think in doing so it alienates significant portion of the
> userbase.
>
>
> --
> Problem reports: http://cygwin.com/problems.html
> FAQ: http://cygwin.com/faq/
> Documentation: http://cygwin.com/docs.html
> Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
>
>
--
Problem reports: http://cygwin.com/problems.html
FAQ: http://cygwin.com/faq/
Documentation: http://cygwin.com/docs.html
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
prev parent reply other threads:[~2019-09-03 5:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-25 17:32 Quanah Gibson-Mount
2019-07-25 18:30 ` openldap on Cygwin (was: Bug report: Killing a native process may not actually kill it) Achim Gratz
2019-07-25 19:04 ` openldap on Cygwin Quanah Gibson-Mount
2019-08-28 15:46 ` Bug report: Killing a native process may not actually kill it Quanah Gibson-Mount
2019-08-28 15:59 ` Corinna Vinschen
2019-08-28 16:02 ` Quanah Gibson-Mount
2019-08-28 20:33 ` Corinna Vinschen
2019-08-28 22:43 ` Kaz Kylheku
2019-08-29 0:02 ` Quanah Gibson-Mount
2019-08-29 1:01 ` Steven Penny
2019-09-03 5:38 ` Ray Donnelly [this message]
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=CAOYw7dsxif5+JpGL+hK91t_owzkgEmY-kRJOP68ignOQXkeaug@mail.gmail.com \
--to=mingw.android@gmail.com \
--cc=cygwin@cygwin.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.
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).