public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Alejandro Colomar <alx.manpages@gmail.com>
To: Sam James <sam@gentoo.org>
Cc: Libc-alpha <libc-alpha@sourceware.org>,
	Job Snijders <job@fastly.com>,
	Florian Weimer <fweimer@redhat.com>, Paul Smith <psmith@gnu.org>,
	Paul Eggert <eggert@cs.ucla.edu>
Subject: Re: copying a string with truncation (was: [PATCH] resolv: add IPv6 support to inet_net_pton())
Date: Fri, 23 Dec 2022 12:45:05 +0100	[thread overview]
Message-ID: <e6a34c79-8481-04b3-4af5-94d6021291e0@gmail.com> (raw)
In-Reply-To: <d5521636-0cea-2e29-21af-32548e1740c2@gmail.com>


[-- Attachment #1.1: Type: text/plain, Size: 1370 bytes --]

Oops, I accidentally CCd the wrong Paul.  I intended to CC Eggert :P  Added.

On 12/23/22 12:42, Alejandro Colomar wrote:
> Hey Sam!
> 
> On 12/23/22 08:00, Sam James wrote:
>>
>>
>>> On 23 Dec 2022, at 06:55, Sam James via Libc-alpha 
>>> <libc-alpha@sourceware.org> wrote:
>>
>>> strlcpy and strlcat is in POSIX next 
>>> (https://www.austingroupbugs.net/view.php?id=986) and will be in glibc
>>> in due course, I believe.
>>>
>>> See https://sourceware.org/bugzilla/show_bug.cgi?id=178. Florian sent a patch 
>>> a few months ago
>>> but I don't think anything happened with it yet 
>>> (https://patchwork.sourceware.org/project/glibc/patch/87fsjp7rqz.fsf@oldenburg.str.redhat.com/).
>>>
>> Ah, I didn't read over the discussion again as I thought I'd remembered it all,
>> but since then, Paul's objection bug w/ austingroup has been closed, so I 
>> don't see
>> a reason not to move forward.
> 
> Ahh, good then.  BTW, could you please link to Paul's objection?  I couldn't 
> find it.  Anyway, I'll CC him.
> 
> I'll reply on the other thread, since I still think we need the other function.
> 
> Cheers,
> 
> Alex
> 
> P.S.:  I think you may have libc-alpha as 'Zack Weinberg via Libc-alpha' on you 
> address book?  Or maybe it's my thunderbird?  I think it's not me.
> 
> 

-- 
<http://www.alejandro-colomar.es/>

[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 833 bytes --]

  reply	other threads:[~2022-12-23 11:45 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-12-22 17:54 [PATCH] resolv: add IPv6 support to inet_net_pton() Job Snijders
2022-12-22 18:21 ` Florian Weimer
2022-12-22 18:28 ` copying a string with truncation (was: [PATCH] resolv: add IPv6 support to inet_net_pton()) Alejandro Colomar
2022-12-22 20:25   ` Alejandro Colomar
2022-12-23  6:55     ` Sam James
2022-12-23  7:00       ` Sam James
2022-12-23 11:42         ` Alejandro Colomar
2022-12-23 11:45           ` Alejandro Colomar [this message]
2022-12-31 15:11           ` Sam James
2023-01-17 10:56 ` [PATCH] resolv: add IPv6 support to inet_net_pton() Job Snijders
2023-04-19 11:31   ` Job Snijders
2024-03-17  1:23 ` Job Snijders
2024-03-17  3:19   ` Job Snijders
2024-03-17 11:18     ` Florian Weimer
2024-03-18  8:59       ` Job Snijders
2024-03-18  9:23         ` Andreas Schwab
2024-03-18 23:01           ` Job Snijders
2024-03-19  8:20             ` Andreas Schwab
2024-03-19  8:29               ` Job Snijders
2024-03-19  9:50                 ` Andreas Schwab
2024-03-22  4:16                   ` Job Snijders
2024-03-22 14:24                     ` Zack Weinberg
2024-03-25  9:04                       ` Job Snijders
2024-04-14 14:56                         ` Job Snijders
2024-04-15  8:15                           ` Xi Ruoyao
2024-03-25  8:45                     ` Andreas Schwab

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=e6a34c79-8481-04b3-4af5-94d6021291e0@gmail.com \
    --to=alx.manpages@gmail.com \
    --cc=eggert@cs.ucla.edu \
    --cc=fweimer@redhat.com \
    --cc=job@fastly.com \
    --cc=libc-alpha@sourceware.org \
    --cc=psmith@gnu.org \
    --cc=sam@gentoo.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;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).