From: Luke Diamand <luke@diamand.org>
To: git@vger.kernel.org
Cc: Yang Zhao <yang.zhao@skyboxlabs.com>,
Eric Sunshine <sunshine@sunshineco.com>,
Luke Diamand <luke@diamand.org>
Subject: [PATCHv1 0/1] git-p4: fix file descriptor leak
Date: Thu, 30 Jan 2020 11:50:33 +0000 [thread overview]
Message-ID: <20200130115034.6191-1-luke@diamand.org> (raw)
Spotted by Eric Sunshine here:
https://public-inbox.org/git/CAPig+cRx3hG64nuDie69o_gdX39F=sR6D8LyA7J1rCErgu0aMA@mail.gmail.com/
There are at least two more of these, but I would prefer to leave them
alone until the python3 changes have been merged.
Luke Diamand (1):
git-p4: avoid leak of file handle when cloning
git-p4.py | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
--
2.20.1.390.gb5101f9297
next reply other threads:[~2020-01-30 11:50 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 11:50 Luke Diamand [this message]
2020-01-30 11:50 ` [PATCHv1 1/1] git-p4: avoid leak of file handle when cloning Luke Diamand
2020-01-30 20:22 ` Junio C Hamano
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=20200130115034.6191-1-luke@diamand.org \
--to=luke@diamand.org \
--cc=git@vger.kernel.org \
--cc=sunshine@sunshineco.com \
--cc=yang.zhao@skyboxlabs.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 NNTP newsgroup(s).