From: Alejandro Colomar <alx@kernel.org>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: linux-man@vger.kernel.org
Subject: Re: [PATCH 1/4] * Remove man3/stpecpyx.3; no longer present.
Date: Mon, 13 Nov 2023 01:18:02 +0100 [thread overview]
Message-ID: <ZVFrOtyoc5WnL7Ws@debian> (raw)
In-Reply-To: <20231112235218.80195-2-eggert@cs.ucla.edu>
[-- Attachment #1: Type: text/plain, Size: 623 bytes --]
Hi Paul,
On Sun, Nov 12, 2023 at 03:52:05PM -0800, Paul Eggert wrote:
Patch applied.
<https://www.alejandro-colomar.es/src/alx/linux/man-pages/man-pages.git/commit/?h=contrib&id=c67f69f50c7e20800113e73b946ff7b2b51f1733>
Thanks,
Alex
> ---
> man3/stpecpyx.3 | 1 -
> 1 file changed, 1 deletion(-)
> delete mode 100644 man3/stpecpyx.3
>
> diff --git a/man3/stpecpyx.3 b/man3/stpecpyx.3
> deleted file mode 100644
> index beb850746..000000000
> --- a/man3/stpecpyx.3
> +++ /dev/null
> @@ -1 +0,0 @@
> -.so man7/string_copying.7
> --
> 2.41.0
>
>
--
<https://www.alejandro-colomar.es/>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2023-11-13 0:18 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-12 23:52 [PATCH 0/4] improvements for strncpy.3 etc Paul Eggert
2023-11-12 23:52 ` [PATCH 1/4] * Remove man3/stpecpyx.3; no longer present Paul Eggert
2023-11-13 0:18 ` Alejandro Colomar [this message]
2023-11-12 23:52 ` [PATCH 2/4] string.3 fixes Paul Eggert
2023-11-13 0:53 ` Alejandro Colomar
2023-11-13 22:27 ` Paul Eggert
2023-11-13 23:25 ` Alejandro Colomar
2023-11-12 23:52 ` [PATCH 3/4] strncat.3 fixes Paul Eggert
2023-11-13 1:15 ` Alejandro Colomar
2023-11-13 16:23 ` Alejandro Colomar
2023-11-21 16:03 ` Alejandro Colomar
2023-11-12 23:52 ` [PATCH 4/4] stpncpy(3) fixes Paul Eggert
2023-11-13 1:29 ` Alejandro Colomar
2023-11-21 18:33 ` Alejandro Colomar
2023-11-21 21:18 ` Paul Eggert
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=ZVFrOtyoc5WnL7Ws@debian \
--to=alx@kernel.org \
--cc=eggert@cs.ucla.edu \
--cc=linux-man@vger.kernel.org \
/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