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.3 required=3.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,FREEMAIL_FORGED_FROMDOMAIN,FREEMAIL_FROM, 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 00D1BC43331 for ; Sun, 29 Mar 2020 07:23:27 +0000 (UTC) Received: from vger.kernel.org (vger.kernel.org [209.132.180.67]) by mail.kernel.org (Postfix) with ESMTP id C429720748 for ; Sun, 29 Mar 2020 07:23:26 +0000 (UTC) Authentication-Results: mail.kernel.org; dkim=pass (2048-bit key) header.d=gmail.com header.i=@gmail.com header.b="dsJ0d21B" Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1727286AbgC2HX0 (ORCPT ); Sun, 29 Mar 2020 03:23:26 -0400 Received: from mail-wr1-f66.google.com ([209.85.221.66]:37683 "EHLO mail-wr1-f66.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1727335AbgC2HX0 (ORCPT ); Sun, 29 Mar 2020 03:23:26 -0400 Received: by mail-wr1-f66.google.com with SMTP id w10so17134117wrm.4 for ; Sun, 29 Mar 2020 00:23:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=cc:subject:to:references:from:message-id:date:user-agent :mime-version:in-reply-to:content-language:content-transfer-encoding; bh=pWBn/hdEFB1tZ80ZhbDpNcynr1W0bkeBR+j3I6jsd2U=; b=dsJ0d21BtohdeA0UuQ7R9wyLAx318n8OYhFDfsC9zfgeujkt5RU+/NWmhIxaHJ5F8U ZNHJNIRKB8GfixsJhym8LoE5pHGBl8B/kUhulqQJPXh5I38dRmrLixB1cu/AOvH0ZNyD 5DM0qR9YOiKDRaAZHfuMRHy+2ln/HNeVqeipcb99nCsmpM3+89JfbNCbyv/Az30eWH2W P619ZbjRkDrw3SPkSlgQ9+mTkV9f9NsLUCvWUz+hQCjUvQJ+zZpxpIevO0rUJC6j8v96 W/bTuylE521dkDlf80JD9KKBRwOchWsNTq0ymKCd8il+NX/CXHEjYRqSPEZhYq/s6mW7 71Tw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:cc:subject:to:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=pWBn/hdEFB1tZ80ZhbDpNcynr1W0bkeBR+j3I6jsd2U=; b=KF4rMpOd56yXcY2IFwkrbQSgTu95C6wuVePuVPRUKSsvtNKLjwGA9ZO8Sx1aD4v7P/ s3yu/307B1Ji2O5CELZ8XrgtglyDjYj3xlE64iAskDA8MZRWhjRz1DycPA+zgdjYfRWb PI2lZmRmCUjU4i8RsZi2h5H/uYmgoaIazTyXAfwAbOXiKRDnly+4eqVgL7SHEnCWomsU 8pJL1UlCxVsRE5rOj5hAfVJ5cwo9dmTIRqYopgEtucZQTPCyXmQwGfOIXIUZN25hr0ms RArlO3bHuWUUbPPVJ3RpgPLhs19qZOaXU9MWLa8Qp0Vjyzitx0x2T5LUAuMBo46ab1RX ujmQ== X-Gm-Message-State: ANhLgQ1Ch1yv51wxMohFm/R5DT0Y3EQfi2uwGc31WVoN8P5zx1Hh/JA+ ffkA4MiMW35+4Ea2VN2w5IcFt9Kg X-Google-Smtp-Source: ADFU+vtVa+JtJ6ZXcGktaNLutl0WtFSxz4Bhrzh1Q2KHJtziWy8ah3/rVN0IfY3254HLLrkyHx8JVA== X-Received: by 2002:adf:ef48:: with SMTP id c8mr8111273wrp.379.1585466604501; Sun, 29 Mar 2020 00:23:24 -0700 (PDT) Received: from ?IPv6:2001:a61:2482:101:3351:6160:8173:cc31? ([2001:a61:2482:101:3351:6160:8173:cc31]) by smtp.gmail.com with ESMTPSA id z129sm15777232wmb.7.2020.03.29.00.23.23 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Sun, 29 Mar 2020 00:23:23 -0700 (PDT) Cc: mtk.manpages@gmail.com, linux-man@vger.kernel.org Subject: Re: Typo in man-page: SIGNAL(7) To: "Pablo M. Ronchi" References: From: "Michael Kerrisk (man-pages)" Message-ID: Date: Sun, 29 Mar 2020 09:23:23 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:68.0) Gecko/20100101 Thunderbird/68.6.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8 Content-Language: en-US Content-Transfer-Encoding: 7bit Sender: linux-man-owner@vger.kernel.org Precedence: bulk List-ID: X-Mailing-List: linux-man@vger.kernel.org On 3/26/20 6:17 PM, Pablo M. Ronchi wrote: > In the URL: > > http://man7.org/linux/man-pages/man7/signal.7.html > > there is the following duplication typo at the end of the paragraph: "it > was it was" (marked in capital letters, below) > > ... > Signal mask and pending signals > ... > A signal may be blocked, which means that it will not be delivered until > it is later unblocked. Between the time when it is generated and when it > is delivered a signal is said to be pending. Each thread in a process > has an independent signal mask, which indicates the set of signals that > the thread is currently blocking. A thread can manipulate its signal > mask using pthread_sigmask(3). In a traditional single-threaded > application, sigprocmask(2) can be used to manipulate the signal mask. A > child created via fork(2) inherits a copy of its parent's signal mask; > the signal mask is preserved across execve(2). 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 signal 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). > ... Thanks, Pablo. Fixed! Cheers, Michael -- Michael Kerrisk Linux man-pages maintainer; http://www.kernel.org/doc/man-pages/ Linux/UNIX System Programming Training: http://man7.org/training/