From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-users@zsh.org
Subject: Re: File descriptor leakage?
Date: Mon, 29 Sep 2014 15:03:35 +0100 [thread overview]
Message-ID: <20140929150335.472ec4b8@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <20140929135851.GA12969@lilyforest>
On Mon, 29 Sep 2014 21:58:51 +0800
lilydjwg <lilydjwg@gmail.com> wrote:
> Hi, I'm sorry I didn't test master. It turns out that this has already
> been fix at commit 4414e54ea7ffe50acca851c11c2ef49dc867c55d
Great.
> And the patch above doesn't fix it for me (patched against that bad commit).
I wouldn't expect it to, since there's no sign anything was actually
failing apart from the leak; it's just tidying up another hole.
pws
prev parent reply other threads:[~2014-09-29 14:13 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-29 3:53 lilydjwg
2014-09-29 6:07 ` Bart Schaefer
2014-09-29 10:47 ` lilydjwg
2014-09-29 10:59 ` Peter Stephenson
2014-09-29 13:58 ` lilydjwg
2014-09-29 14:03 ` Peter Stephenson [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=20140929150335.472ec4b8@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-users@zsh.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.vuxu.org/mirror/zsh/
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 NNTP newsgroup(s).