public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Mike Frysinger <vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
To: Petr Baudis <pasky-AlSwsSmVLrQ@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: Fri, 5 Mar 2010 14:46:13 -0500	[thread overview]
Message-ID: <201003051446.14847.vapier@gentoo.org> (raw)
In-Reply-To: <20100224204625.GD19115-DDGJ70k9y3lX+M3pkMnKjw@public.gmane.org>

[-- Attachment #1: Type: Text/Plain, Size: 451 bytes --]

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.
-mike

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

  parent reply	other threads:[~2010-03-05 19:46 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 [this message]
     [not found]     ` <201003051446.14847.vapier-aBrp7R+bbdUdnm+yROfE0A@public.gmane.org>
2010-03-05 23:43       ` Petr Baudis

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=201003051446.14847.vapier@gentoo.org \
    --to=vapier-abrp7r+bbdudnm+yrofe0a@public.gmane.org \
    --cc=linux-man-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=mtk.manpages-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org \
    --cc=pasky-AlSwsSmVLrQ@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