From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <SRS0=zzzS=6E=vger.kernel.org=linux-man-owner@kernel.org>
X-Spam-Checker-Version: SpamAssassin 3.4.0 (2014-02-07) on
	aws-us-west-2-korg-lkml-1.web.codeaurora.org
X-Spam-Level: 
X-Spam-Status: No, score=-2.2 required=3.0 tests=HEADER_FROM_DIFFERENT_DOMAINS,
	MAILING_LIST_MULTI,SPF_HELO_NONE,SPF_PASS,USER_AGENT_SANE_1 autolearn=no
	autolearn_force=no version=3.4.0
Received: from mail.kernel.org (mail.kernel.org [198.145.29.99])
	by smtp.lore.kernel.org (Postfix) with ESMTP id 645D7C3815B
	for <linux-man@archiver.kernel.org>; Mon, 20 Apr 2020 08:49:40 +0000 (UTC)
Received: from vger.kernel.org (vger.kernel.org [23.128.96.18])
	by mail.kernel.org (Postfix) with ESMTP id 4CA3220A8B
	for <linux-man@archiver.kernel.org>; Mon, 20 Apr 2020 08:49:40 +0000 (UTC)
Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand
        id S1726006AbgDTItk (ORCPT <rfc822;linux-man@archiver.kernel.org>);
        Mon, 20 Apr 2020 04:49:40 -0400
Received: from smtpout1.mo529.mail-out.ovh.net ([178.32.125.2]:38727 "EHLO
        smtpout1.mo529.mail-out.ovh.net" rhost-flags-OK-OK-OK-OK)
        by vger.kernel.org with ESMTP id S1725865AbgDTItj (ORCPT
        <rfc822;linux-man@vger.kernel.org>); Mon, 20 Apr 2020 04:49:39 -0400
Received: from mxplan6.mail.ovh.net (unknown [10.109.146.239])
        by mo529.mail-out.ovh.net (Postfix) with ESMTPS id 8B41E306BC0F;
        Mon, 20 Apr 2020 10:49:37 +0200 (CEST)
Received: from jwilk.net (37.59.142.96) by DAG4EX2.mxp6.local (172.16.2.32)
 with Microsoft SMTP Server (version=TLS1_2,
 cipher=TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256) id 15.1.1779.2; Mon, 20 Apr
 2020 10:49:36 +0200
Date:   Mon, 20 Apr 2020 10:49:32 +0200
From:   Jakub Wilk <jwilk@jwilk.net>
To:     Michael Kerrisk <mtk.manpages@gmail.com>
CC:     Helge Kreutzmann <debian@helgefjell.de>,
        <linux-man@vger.kernel.org>
Subject: Re: Errors in man pages, here: signal(7): Sentence to long
Message-ID: <20200420084932.xvz32vuv7uqudyih@jwilk.net>
References: <20200419064825.GA32002@Debian-50-lenny-64-minimal>
 <0f760556-f587-fbb0-581c-d0f5a38ad23e@gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"; format=flowed
Content-Disposition: inline
In-Reply-To: <0f760556-f587-fbb0-581c-d0f5a38ad23e@gmail.com>
User-Agent: NeoMutt/20180716
X-Originating-IP: [37.59.142.96]
X-ClientProxiedBy: DAG8EX2.mxp6.local (172.16.2.72) To DAG4EX2.mxp6.local
 (172.16.2.32)
X-Ovh-Tracer-GUID: 3d488a0f-703d-4259-87db-0943038ee1cf
X-Ovh-Tracer-Id: 7070932890502354909
X-VR-SPAMSTATE: OK
X-VR-SPAMSCORE: 0
X-VR-SPAMCAUSE: gggruggvucftvghtrhhoucdtuddrgeduhedrgeefgddtjecutefuodetggdotefrodftvfcurfhrohhfihhlvgemucfqggfjpdevjffgvefmvefgnecuuegrihhlohhuthemucehtddtnecunecujfgurhepfffhvffukfhfgggtuggjfghisehttdertddtredvnecuhfhrohhmpeflrghkuhgsucghihhlkhcuoehjfihilhhksehjfihilhhkrdhnvghtqeenucfkpheptddrtddrtddrtddpfeejrdehledrudegvddrleeinecuvehluhhsthgvrhfuihiivgeptdenucfrrghrrghmpehmohguvgepshhmthhpqdhouhhtpdhhvghlohepmhigphhlrghniedrmhgrihhlrdhovhhhrdhnvghtpdhinhgvtheptddrtddrtddrtddpmhgrihhlfhhrohhmpehjfihilhhksehjfihilhhkrdhnvghtpdhrtghpthhtoheplhhinhhugidqmhgrnhesvhhgvghrrdhkvghrnhgvlhdrohhrgh
Sender: linux-man-owner@vger.kernel.org
Precedence: bulk
List-ID: <linux-man.vger.kernel.org>
X-Mailing-List: linux-man@vger.kernel.org

* Michael Kerrisk (man-pages) <mtk.manpages@gmail.com>, 2020-04-20, 10:33:
>>"A signal may be generated (and thus pending)  for a process as a whole (e."
>>"g., when sent using B<kill>(2))  or for a specific thread (e.g., certain "
>>"signals, such as B<SIGSEGV> and B<SIGFPE>, generated as a consequence of "
>>"executing a specific machine-language instruction are thread directed, as "
>>"are signals targeted at a specific thread using B<pthread_kill>(3)).  A "
>>"process-directed signal may be delivered to any one of the threads that does "
>>"not currently have the signal blocked.  If more than one of the threads has "
>>"the signal unblocked, then the kernel chooses an arbitrary thread to which "
>>"to deliver the signal."
>
>I can't find the text referred to. I think you may be working
>with an older version of the page. Can you please check.

In 3b9d44099f234e8e, the long sentence was replaced with this paragraph:

"A signal may be process-directed or thread-directed. A process-directed 
signal is one that is targeted at (and thus pending for) the process as 
a whole. A signal may be process-directed because it was generated by 
the kernel for reasons other than a hardware exception, or because it 
was sent using kill(2) or sigqueue(3). A thread-directed signals is one 
that is targeted at a specific thread. A signal may be thread-directed 
because it was generated as a consequence of executing a specific 
machine-language instruction that triggered a hardware exception (e.g., 
SIGSEGV for an invalid memory access, or SIGFPE for a math error), or 
because it was it was targeted at a specific thread using interfaces 
such as tgkill(2) or pthread_kill(3).

-- 
Jakub Wilk