From: Joan Karadimov <joan.karadimov@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Simon Morgan <sjm@sjm.io>,
Bozhidar Batsov <bozhidar.batsov@gmail.com>,
15983@debbugs.gnu.org
Subject: bug#15983: 24.3; Emacs Not Killing Child Process
Date: Mon, 23 Dec 2013 18:02:12 +0200 [thread overview]
Message-ID: <CAGVACNW6sTouWp98PTK5HVJ27_0LoXuvGVU+t3JSdpV-D1rDSQ@mail.gmail.com> (raw)
In-Reply-To: <83mwjt8rtd.fsf@gnu.org>
[-- Attachment #1: Type: text/plain, Size: 792 bytes --]
>
> > > > > This might be "good enough" -- we err on the safe side, and only
> leave
> > > > > some subprocesses not killed in rare situations. Does this
> strategy
> > > > > solve the problem which started this bug report?
> > >
> > > You didn't answer that question, but I assume the answer is YES.
> > >
> > It should fix the problem, yes.
>
> Well, I'd prefer a test, to be sure.
>
> Next few days I will be spending less time on this. I'll have something
testable
a few days after Christmas.
Btw, if the patch is going to be substantial, we will need legal
> paperwork from you, before we can accept the code.
>
Yes, I know. This is forming to be larger than I initially thought. Maybe
once
I am done we can evaluate just how big the change set is and I'll do the
paperwork if needed.
[-- Attachment #2: Type: text/html, Size: 1500 bytes --]
prev parent reply other threads:[~2013-12-23 16:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-27 17:47 bug#15983: 24.3; Emacs Not Killing Child Process sjm
2013-11-27 21:02 ` Eli Zaretskii
2013-12-19 15:44 ` Joan Karadimov
2013-12-19 15:56 ` bug#15983: Fw: " Bozhidar Batsov
2013-12-19 17:24 ` Eli Zaretskii
2013-12-20 22:28 ` Joan Karadimov
2013-12-21 8:15 ` Eli Zaretskii
2013-12-21 16:22 ` Joan Karadimov
2013-12-21 18:38 ` Eli Zaretskii
2013-12-22 2:03 ` Joan Karadimov
2013-12-22 3:53 ` Eli Zaretskii
2013-12-23 16:02 ` Joan Karadimov [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
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=CAGVACNW6sTouWp98PTK5HVJ27_0LoXuvGVU+t3JSdpV-D1rDSQ@mail.gmail.com \
--to=joan.karadimov@gmail.com \
--cc=15983@debbugs.gnu.org \
--cc=bozhidar.batsov@gmail.com \
--cc=eliz@gnu.org \
--cc=sjm@sjm.io \
/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).