From: <tomas@tuxteam.de>
To: David Mozes <david.mozes@silk.us>
Cc: "libc-help@sourceware.org" <libc-help@sourceware.org>
Subject: Re: Libc-help Digest, Vol 30, Issue 12
Date: Tue, 30 Aug 2022 18:11:33 +0200 [thread overview]
Message-ID: <Yw42tWE6zkJDn3YR@tuxteam.de> (raw)
In-Reply-To: <AM9PR04MB8291E7D1B77B95BCB3E84234F1799@AM9PR04MB8291.eurprd04.prod.outlook.com>
[-- Attachment #1: Type: text/plain, Size: 463 bytes --]
On Tue, Aug 30, 2022 at 03:14:39PM +0000, David Mozes via Libc-help wrote:
> Hi,
> Am I wondering if the below bug already fixed?
> If yes, what is the commit number
>
> Thx
> David
>
> https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=986724
Have you read the corresponding libc bugzilla entry? It's here.
Much more informative. BTW, it is linked from the above:
https://sourceware.org/bugzilla/show_bug.cgi?id=25847
Cheers
--
tomás
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2022-08-30 16:11 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.44.1661256004.1839035.libc-help@sourceware.org>
2022-08-30 15:14 ` David Mozes
2022-08-30 16:11 ` tomas [this message]
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=Yw42tWE6zkJDn3YR@tuxteam.de \
--to=tomas@tuxteam.de \
--cc=david.mozes@silk.us \
--cc=libc-help@sourceware.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).