From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on dcvr.yhbt.net X-Spam-Level: X-Spam-ASN: AS17314 8.43.84.0/22 X-Spam-Status: No, score=-4.3 required=3.0 tests=AWL,BAYES_00,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,DKIM_VALID_EF,MAILING_LIST_MULTI,NICE_REPLY_A, RCVD_IN_DNSWL_MED,SPF_HELO_PASS,SPF_PASS shortcircuit=no autolearn=ham autolearn_force=no version=3.4.2 Received: from sourceware.org (server2.sourceware.org [8.43.85.97]) (using TLSv1.3 with cipher TLS_AES_256_GCM_SHA384 (256/256 bits) key-exchange X25519 server-signature RSA-PSS (4096 bits) server-digest SHA256) (No client certificate requested) by dcvr.yhbt.net (Postfix) with ESMTPS id 5BD221F8C6 for ; Thu, 5 Aug 2021 06:58:58 +0000 (UTC) Received: from server2.sourceware.org (localhost [IPv6:::1]) by sourceware.org (Postfix) with ESMTP id 2E5EB385C409 for ; Thu, 5 Aug 2021 06:58:57 +0000 (GMT) DKIM-Filter: OpenDKIM Filter v2.11.0 sourceware.org 2E5EB385C409 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=sourceware.org; s=default; t=1628146737; bh=qAhLaNGjFbLRH1f7vlsJsR9uQpjCBvYKVyPcy0Jjr7M=; h=Subject:To:References:Date:In-Reply-To:List-Id:List-Unsubscribe: List-Archive:List-Post:List-Help:List-Subscribe:From:Reply-To:Cc: From; b=mGR/oKABwmSmvn+xVL+iYwC0bdJjS9lXbsuILJNNIR6s+sDZBig3ZobB8PrKVRwIK Lv5U5eLLMi3jPQL3YJTs0pTbrBZPgQLHDKXQpYFaAnRWIVG4vVxCvreDJC7R1826M3 KLKNqBo4AADh3tK/a1ftQwIQjrR457ofxoCAfDmQ= Received: from mail-wr1-x42a.google.com (mail-wr1-x42a.google.com [IPv6:2a00:1450:4864:20::42a]) by sourceware.org (Postfix) with ESMTPS id 7DC02385C409 for ; Thu, 5 Aug 2021 06:58:36 +0000 (GMT) DMARC-Filter: OpenDMARC Filter v1.4.1 sourceware.org 7DC02385C409 Received: by mail-wr1-x42a.google.com with SMTP id c9so5065473wri.8 for ; Wed, 04 Aug 2021 23:58:36 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:subject:to:cc:references:from:message-id:date :user-agent:mime-version:in-reply-to:content-language :content-transfer-encoding; bh=qAhLaNGjFbLRH1f7vlsJsR9uQpjCBvYKVyPcy0Jjr7M=; b=tY/2AwZbgqkM7S6MCmS8MXj56sS68ihnf58Y8NzF7btjKNsmMGUe+5mptlMMg2EzZ2 hsCjzme7ukzUAkZl2MaEFQAqiGMfd0sLcjLhMq1cL9ukxmFnpJS8IWAiVal5bJrUVVJV /1q8TWi73/U+A1QXBQtrHjA7gFt19DmUFVQv2nqSlwTlGM2D3WOYKAEfxYl8NqSGHqxx cWqI3LoKwaOjcIlNP3S7B1S6oPQnvic7Ek46sM5fN2J2MFlSma1jG8/Z7BWIpxvkHjnz Ed+mub+nOBIgvcBZsmPqPMdZ8Mk3G3ciuYiWZkc2k0Hr6omIC1p2nLVrYHhBXxhGs1rp z/Ug== X-Gm-Message-State: AOAM533rqU3Hx28MeyCnmaOHVCBjrvGughPQdbubIupWuenFhALvJJiB shxZaki/t5Xw259mDvRPvZ0= X-Google-Smtp-Source: ABdhPJyrHxt1K8whnrXYJdFD4u4Mf749EclemcvvzhHNDjny6KdQghXvsBYZi7VtxIw4PAgL94rh8A== X-Received: by 2002:adf:eb4a:: with SMTP id u10mr3266641wrn.11.1628146715687; Wed, 04 Aug 2021 23:58:35 -0700 (PDT) Received: from [10.8.0.10] ([195.53.121.100]) by smtp.gmail.com with ESMTPSA id h4sm5231843wru.2.2021.08.04.23.58.34 (version=TLS1_3 cipher=TLS_AES_128_GCM_SHA256 bits=128/128); Wed, 04 Aug 2021 23:58:35 -0700 (PDT) Subject: Re: [patch] nscd.conf.5: describe reloading, clarifications To: Greg Banks References: <02da5334-1635-8aa9-c4e6-deb0161a848d@gmail.com> Message-ID: <01329467-8747-ec5a-6f92-a5466ed64eed@gmail.com> Date: Thu, 5 Aug 2021 08:58:33 +0200 User-Agent: Mozilla/5.0 (X11; Linux x86_64; rv:78.0) Gecko/20100101 Thunderbird/78.12.0 MIME-Version: 1.0 In-Reply-To: Content-Type: text/plain; charset=utf-8; format=flowed Content-Language: en-US Content-Transfer-Encoding: 8bit X-BeenThere: libc-alpha@sourceware.org X-Mailman-Version: 2.1.29 Precedence: list List-Id: Libc-alpha mailing list List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , From: "Alejandro Colomar \(man-pages\) via Libc-alpha" Reply-To: "Alejandro Colomar \(man-pages\)" Cc: "G. Branden Robinson" , "linux-man@vger.kernel.org" , "libc-alpha@sourceware.org" , Michael Kerrisk Errors-To: libc-alpha-bounces+e=80x24.org@sourceware.org Sender: "Libc-alpha" CC += Branden Hi Greg, On 8/4/21 3:40 PM, Greg Banks wrote: > Hi Alejandro, > > > Could you please use the same method you used for sending v1 to send > an v3? \ > > I did but apparently the email stack at my end insists on adding some > randomness to its behavior.  I'm going to try and step outside this > email text damage drama and send a pull request separately. Hmm, not good. The worst part is that as your emails are not plain text, they don't reach the mailing list (only the first one did). If you can't solve it (I suggest using git-send-email(1), to avoid that randomness), I suggest that you send the email anyway as good as you can (better send it both inline and as an attachment, so that it is more likely that one of them will apply), and if it applies to my tree, I'll apply it and also forward it to the list as plain text. > >> Also, please see some comments below. > > Applied, thanks. > >> >> +.PP >> >> That's not correct.  Did you copy that from another place?  If so, >> please tell me because I should fix it. > > No, it's a habit left over from the last time I contributed to this > project (in 2008).  It seems the rules have changed. > >> We use that between paragraphs, but not before the first one nor after >> the last one. > > Ok, sure, but in that case the description of .PP in man(7) is wrong > >        .PP      Begin a new paragraph and reset prevailing indent. That's something that I had pending to address from Branden. That page is a mix of things that should go into man-pages(7), groff_man_style(7), and groff_man(7), and then man(7) should be removed and replaced by a link page to groff_man(7). For now, You can read groff_man(7) (provided by the groff package), which tells us that .SH already does what .PP does (start a clean paragraph) (and it does more things, of course). The thing is that if you add .PP after .SH you will have a blank line (and this an exercise of my mental groff, which I hope doesn't fail me this time), and it would be a bit weird to have a blank line after the section title. Thanks, Alex -- Alejandro Colomar Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/ http://www.alejandro-colomar.es/