From: Petr Baudis <pasky-AlSwsSmVLrQ@public.gmane.org>
To: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
Cc: mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org,
linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Subject: Re: [PATCH] setenv.3, putenv.3: Elaborate on thread (non-)safety
Date: Sat, 6 Mar 2010 00:43:02 +0100 [thread overview]
Message-ID: <20100305234302.GI5075@machine.or.cz> (raw)
In-Reply-To: <201003051446.14847.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
On Fri, Mar 05, 2010 at 02:46:13PM -0500, Mike Frysinger wrote:
> On Wednesday 24 February 2010 15:46:25 Petr Baudis wrote:
> > +thus consults $TZ deep inside). Thus, modifying environment
> > +in multi-threaded applications should be avoided if at all possible,
>
> modifying environment -> modifying the environment
>
> > +or special measures taken so that no non-obvious library functions
> > +get called meanwhile.
>
> "no non" is funky. how about:
> so that non-obvious library functions are not called in the meanwhile.
Good catches in both cases, thanks!
--
Petr "Pasky" Baudis
http://pasky.or.cz/ | "Ars longa, vita brevis." -- Hippocrates
--
To unsubscribe from this list: send the line "unsubscribe linux-man" in
the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2010-03-05 23:43 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-24 20:46 [PATCH] setenv.3, putenv.3: Elaborate on thread (non-)safety Petr Baudis
[not found] ` <20100224204625.GD19115-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>
2010-03-05 19:46 ` Mike Frysinger
[not found] ` <201003051446.14847.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2010-03-05 23:43 ` Petr Baudis [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=20100305234302.GI5075@machine.or.cz \
--to=pasky-alswssmvlrq@public.gmane.org \
--cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
--cc=vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox