From: Peter Stephenson <p.stephenson@samsung.com>
To: zsh-workers@zsh.org
Subject: Re: [PATCH] make sure internal temp files are user readable and writeable
Date: Tue, 27 Mar 2018 09:34:25 +0100 [thread overview]
Message-ID: <20180327093425.5a7e144c@camnpupstephen.cam.scsc.local> (raw)
In-Reply-To: <41233f43-9695-3b82-888f-5cad9cb2ca47@inlv.org>
On Mon, 26 Mar 2018 22:32:50 +0200
Martijn Dekker <martijn@inlv.org> wrote:
> Today was apparently not my best day. Since that function was already
> blocking (a.k.a. queueing) signals to do its thing, of course my patch
> was trivial to fix. Take 2.
Couldn't see any obvious problem with that, so I've committed it.
Thanks
pws
prev parent reply other threads:[~2018-03-27 8:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-03-26 16:45 Martijn Dekker
2018-03-26 17:00 ` Stephane Chazelas
2018-03-26 17:37 ` Martijn Dekker
2018-03-26 20:32 ` Martijn Dekker
2018-03-27 8:34 ` 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=20180327093425.5a7e144c@camnpupstephen.cam.scsc.local \
--to=p.stephenson@samsung.com \
--cc=zsh-workers@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).