From patchwork Thu Dec 27 22:13:25 2018 Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit X-Patchwork-Submitter: Rafal Luzynski X-Patchwork-Id: 30871 Received: (qmail 41440 invoked by alias); 27 Dec 2018 22:14:44 -0000 Mailing-List: contact libc-alpha-help@sourceware.org; run by ezmlm Precedence: bulk List-Id: List-Unsubscribe: List-Subscribe: List-Archive: List-Post: List-Help: , Sender: libc-alpha-owner@sourceware.org Delivered-To: mailing list libc-alpha@sourceware.org Received: (qmail 41426 invoked by uid 89); 27 Dec 2018 22:14:43 -0000 Authentication-Results: sourceware.org; auth=none X-Spam-SWARE-Status: No, score=-23.7 required=5.0 tests=BAYES_00, GIT_PATCH_0, GIT_PATCH_1, GIT_PATCH_2, GIT_PATCH_3, KAM_LAZY_DOMAIN_SECURITY, RCVD_IN_DNSWL_NONE, XPRIO autolearn=ham version=3.3.2 spammy=H*x:Mailer, H*UA:Mailer, Hx-languages-length:1031 X-HELO: shared-ano163.rev.nazwa.pl X-Spam-Score: -1 Date: Thu, 27 Dec 2018 23:13:25 +0100 (CET) From: Rafal Luzynski To: libc-alpha@sourceware.org Message-ID: <1021853475.594941.1545948806002@poczta.nazwa.pl> Subject: [PATCH] NEWS: Fix a minor typo ("incosistent" -> "inconsistent"). MIME-Version: 1.0 This looks like an obvious fix but I'm asking for confirmation just in case. OK for master now? While at this, "multithread environment" or "multithreaded environment"? Regards, Rafal From: Rafal Luzynski Date: Thu, 27 Dec 2018 23:04:14 +0100 --- NEWS | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) * Support for the C-SKY ABIV2 running on Linux has been added. This port diff --git a/NEWS b/NEWS index 4a24d9f..454de5b 100644 --- a/NEWS +++ b/NEWS @@ -43,7 +43,7 @@ Major new features: * The popen and system do not run atfork handlers anymore (BZ#17490). Although it is a possible POSIX violation, the POSIX rationale in pthread_atfork documentation regarding atfork handlers is to handle - incosistent mutex state after fork call in multithread environment. + inconsistent mutex state after fork call in multithread environment. In both popen and system there is no direct access to user-defined mutexes.