From: "Alejandro Colomar (man-pages)" <alx.manpages@gmail.com>
To: Greg Banks <gbanks@linkedin.com>
Cc: Michael Kerrisk <mtk.manpages@gmail.com>,
"linux-man@vger.kernel.org" <linux-man@vger.kernel.org>,
DJ Delorie <dj@redhat.com>,
"libc-alpha@sourceware.org" <libc-alpha@sourceware.org>
Subject: Re: [pr] nscd.conf.5: describe reloading, clarifications, v3
Date: Thu, 5 Aug 2021 09:04:05 +0200 [thread overview]
Message-ID: <0c851411-caf6-5178-09c5-f5d54fb12c97@gmail.com> (raw)
In-Reply-To: <BL0PR2101MB13165DA16EA08B6ECF60D1CAA1F19@BL0PR2101MB1316.namprd21.prod.outlook.com>
Hi greg,
On 8/4/21 3:46 PM, Greg Banks wrote:
> The following changes since commit 4a4b5ecfe1f8c5b5f7eaf0e28778db6c6991ae33:
>
> nscd.conf.5: describe reloading, clarifications, v3 (2021-08-04 06:17:39 -0700)
>
> are available in the Git repository at:
>
> git@github.com:gnb/man-pages.git nscd.conf.5
>
> for you to fetch changes up to 4a4b5ecfe1f8c5b5f7eaf0e28778db6c6991ae33:
>
> nscd.conf.5: describe reloading, clarifications, v3 (2021-08-04 06:17:39 -0700)
>
> ----------------------------------------------------------------
>
Okay, this works. Could you please do this and also send the patch to
the list inline (that way it's easier to comment)? If it is reformatted
and doesn't arrive to the list, I'll forward it.
About the patch itself, please respect the right margin at column 80,
and also s/i.e./i.e.,/
Thanks,
Alex
--
Alejandro Colomar
Linux man-pages comaintainer; https://www.kernel.org/doc/man-pages/
http://www.alejandro-colomar.es/
next prev parent reply other threads:[~2021-08-05 7:04 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-08-04 13:46 [pr] nscd.conf.5: describe reloading, clarifications, v3 Greg Banks
2021-08-05 7:04 ` Alejandro Colomar (man-pages) [this message]
[not found] ` <BL0PR2101MB1316CCF8B96DDEC9D0D5F5D4A1F29@BL0PR2101MB1316.namprd21.prod.outlook.com>
2021-08-06 7:25 ` Alejandro Colomar (man-pages)
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0c851411-caf6-5178-09c5-f5d54fb12c97@gmail.com \
--to=alx.manpages@gmail.com \
--cc=dj@redhat.com \
--cc=gbanks@linkedin.com \
--cc=libc-alpha@sourceware.org \
--cc=linux-man@vger.kernel.org \
--cc=mtk.manpages@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).