From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: 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,URIBL_BLOCKED,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 B460AC54FCB for ; Fri, 24 Apr 2020 18:50:39 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [23.128.96.18]) by mail.kernel.org (Postfix) with ESMTP id 963E12075A for ; Fri, 24 Apr 2020 18:50:39 +0000 (UTC) Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1728649AbgDXSuj (ORCPT ); Fri, 24 Apr 2020 14:50:39 -0400 Received: from luckmann.name ([213.239.213.133]:54685 "EHLO static.213-239-213-133.clients.your-server.de" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1728379AbgDXSuj (ORCPT ); Fri, 24 Apr 2020 14:50:39 -0400 Received: from localhost (localhost [127.0.0.1]) (uid 502) by static.213-239-213-133.clients.your-server.de with local id 0000000000E56011.000000005EA334FC.00001FB5; Fri, 24 Apr 2020 20:50:36 +0200 Date: Fri, 24 Apr 2020 20:50:36 +0200 From: Helge Kreutzmann To: "Michael Kerrisk (man-pages)" Cc: Jakub Wilk , linux-man Subject: Re: Errors in man pages, here: signal(7): Sentence to long Message-ID: <20200424185036.GC7401@Debian-50-lenny-64-minimal> References: <20200419064825.GA32002@Debian-50-lenny-64-minimal> <0f760556-f587-fbb0-581c-d0f5a38ad23e@gmail.com> <20200420084932.xvz32vuv7uqudyih@jwilk.net> Mime-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="=_luckmann.name-8117-1587754236-0001-2" Content-Disposition: inline In-Reply-To: X-Public-Key-URL: http://www.helgefjell.de/data/debian_neu.asc X-homepage: http://www.helgefjell.de/debian User-Agent: Mutt/1.10.1 (2018-07-13) Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org This is a MIME-formatted message. If you see this text it means that your E-mail software does not support MIME-formatted messages. --=_luckmann.name-8117-1587754236-0001-2 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline Content-Transfer-Encoding: quoted-printable Hello Michael, On Mon, Apr 20, 2020 at 10:51:00AM +0200, Michael Kerrisk (man-pages) wrote: > On Mon, 20 Apr 2020 at 10:49, Jakub Wilk wrote: > > > > * Michael Kerrisk (man-pages) , 2020-04-20, 10:= 33: > > >>"A signal may be generated (and thus pending) for a process as a who= le (e." > > >>"g., when sent using B(2)) or for a specific thread (e.g., cer= tain " > > >>"signals, such as B and B, generated as a consequenc= e of " > > >>"executing a specific machine-language instruction are thread directe= d, as " > > >>"are signals targeted at a specific thread using B(3)).= A " > > >>"process-directed signal may be delivered to any one of the threads t= hat does " > > >>"not currently have the signal blocked. If more than one of the thre= ads 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). >=20 > Thanks, Jakub. Thanks.=20 We are working with what our upstreams provide, and especially archlinux tries to update frequently (but we might lag a few weeks behind them), so from time to time the issue might already been fixed. Due to the sheer size of upstreams and man pages and potential issues to be fixed we unfortunately might occasionally thus report issues already dealt with by you (or your fellow maintainers of other projects). Sorry for the noise. Greetings Helge --=20 Dr. Helge Kreutzmann debian@helgefjell.de Dipl.-Phys. http://www.helgefjell.de/debian.php 64bit GNU powered gpg signed mail preferred Help keep free software "libre": http://www.ffii.de/ --=_luckmann.name-8117-1587754236-0001-2 Content-Type: application/pgp-signature; name="signature.asc" Content-Transfer-Encoding: 7bit -----BEGIN PGP SIGNATURE----- iQIzBAABCAAdFiEEbZZfteMW0gNUynuwQbqlJmgq5nAFAl6jNPwACgkQQbqlJmgq 5nBBaA/+IIVdbOrzeISkev2i0E55rIY/Z3+PSEV6fyeFTcjQi23EaX3LTrqAsEbo nkSMJSd2HuvNZqVQYkVZxScISRGFPN0rXYmaKn6Ad3HY1gAUWth8Cvo7NoJputnS qqZ19n3XxjnCJmjT3g1IKZhTJSX6/SisBZTtTIFeQtouNMcfp3NmHW8JL9SUDKFn ImhpXZ4KUo1Dm6ArsW3bRSRSKYXOmEuEHQoZKk2t7pl65dwltucz4xRNwmm7rJXT E6a4GnWMD6c4IDwO950OD1qAHhbcXrDwQ4uIUQw/ahwa9PdWIMqvfNbtE7Q0qUYE GbVFHsX62y+ADCbdj4n+YFDHdS0nw8FIh9F5cCjHCf0Nt/M7jWex3PPVTFC92J27 3aKnNX/LpRtFEJGBFkSjgZSnsOWBlluFBQ9OC+fAO/utQ0WnrM15WOqsv225D74O 6sKkkG1lJ/zgIc3z0v/jxsSruDc3c+rU7Y6jX8sdzinMOuWddbqyhc2rZaca3vLa SWLPxs/gGC6C8OxV9XI/bVxRKdFe5ywkUj9R6q2F+RZw0a3xsNyabx69fPVccewW YMu6wcBQpwjGgoo6enekJ5EOhFNfYisb4ZGDLQPcmT0gA5G6Wmf/Y0o/OUd9oyfC hTuRqBXcsY5B9mPU/lSXN6YaOTxr1KZ+URg6ppSH/IJMaKCpjR0= =LlIz -----END PGP SIGNATURE----- --=_luckmann.name-8117-1587754236-0001-2--