From: Xi Ruoyao <xry111@xry111.site>
To: Job Snijders <job@fastly.com>, Zack Weinberg <zack@owlfolio.org>
Cc: Andreas Schwab <schwab@suse.de>,
Florian Weimer <fweimer@redhat.com>,
GNU libc development <libc-alpha@sourceware.org>
Subject: Re: [PATCH] resolv: add IPv6 support to inet_net_pton()
Date: Mon, 15 Apr 2024 16:15:52 +0800 [thread overview]
Message-ID: <9e106425372ba08e7f13c621c99177aa771f03de.camel@xry111.site> (raw)
In-Reply-To: <ZhvujHUW8U_HqZ3Z@snel>
On Sun, 2024-04-14 at 16:56 +0200, Job Snijders wrote:
> Dear all,
>
> Are there any other comments, or can this be considered for merging?
Send the updated patch as [PATCH v2] instead of just a follow up. Or
patchwork won't track the updated version and people are unlikely to
ever notice it.
--
Xi Ruoyao <xry111@xry111.site>
School of Aerospace Science and Technology, Xidian University
next prev parent reply other threads:[~2024-04-15 8:16 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-22 17:54 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
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 [this message]
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=9e106425372ba08e7f13c621c99177aa771f03de.camel@xry111.site \
--to=xry111@xry111.site \
--cc=fweimer@redhat.com \
--cc=job@fastly.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
--cc=zack@owlfolio.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).