From: Florian Weimer <fweimer@redhat.com>
To: Andreas Schwab <schwab@suse.de>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH] Add test for bug 29530
Date: Mon, 29 Aug 2022 17:02:29 +0200 [thread overview]
Message-ID: <87fshf2iuy.fsf@oldenburg.str.redhat.com> (raw)
In-Reply-To: <mvm35dfcdix.fsf@suse.de> (Andreas Schwab's message of "Mon, 29 Aug 2022 16:47:34 +0200")
* Andreas Schwab:
> This tests for a bug that was introduced in commit edc1686af0 ("vfprintf:
> Reuse work_buffer in group_number") and fixed as a side effect of commit
> 6caddd34bd ("Remove most vfprintf width/precision-dependent allocations
> (bug 14231, bug 26211).").
> ---
> stdio-common/Makefile | 2 ++
> stdio-common/tst-grouping2.c | 39 ++++++++++++++++++++++++++++++++++++
> 2 files changed, 41 insertions(+)
> create mode 100644 stdio-common/tst-grouping2.c
Okay, thanks.
Florian
prev parent reply other threads:[~2022-08-29 15:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 13:34 Andreas Schwab
2022-08-29 14:02 ` Florian Weimer
2022-08-29 14:18 ` Andreas Schwab
2022-08-29 14:47 ` Andreas Schwab
2022-08-29 15:02 ` Florian Weimer [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=87fshf2iuy.fsf@oldenburg.str.redhat.com \
--to=fweimer@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=schwab@suse.de \
/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).