From: TAMUKI Shoichi <tamuki@linet.gr.jp>
To: Carlos O'Donell <carlos@redhat.com>,
Rafal Luzynski <digitalfreak@lingonborough.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
libc-alpha@sourceware.org
Subject: Re: 2.29 freeze update: Last fortnight
Date: Thu, 17 Jan 2019 15:30:40 +0900 [thread overview]
Message-ID: <201901170630.AA04185@tamuki.linet.gr.jp> (raw)
In-Reply-To: <0d64eb25-cd96-be30-2ba3-e735f85e4e35@redhat.com>
Hello Carlos,
From: Carlos O'Donell <carlos@redhat.com>
To: Rafal Luzynski <digitalfreak@lingonborough.com>,
Siddhesh Poyarekar <siddhesh@gotplt.org>,
GLIBC Devel <libc-alpha@sourceware.org>
Cc: Joseph Myers <joseph@codesourcery.com>
Subject: Re: 2.29 freeze update: Last fortnight
Date: Tue, 15 Jan 2019 12:09:03 -0500
> > Question: do we need a separate bug report to fix the additional flags
> > being ignored (like "%-EY" and "%_EY") or does it fall in the same
> > general category "improve the width of %EY"?
>
> Please file a new bug for this. This is a distinct issue.
I have created a new Bugzilla report for this.
https://sourceware.org/bugzilla/show_bug.cgi?id=24096
Regards,
TAMUKI Shoichi
next prev parent reply other threads:[~2019-01-17 6:31 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-15 14:37 2.29 freeze update: Last fortnight Siddhesh Poyarekar
2019-01-15 16:52 ` Rafal Luzynski
2019-01-15 17:02 ` Zack Weinberg
2019-01-15 17:16 ` Rafal Luzynski
2019-01-15 17:49 ` Paul Eggert
2019-01-15 18:16 ` Rafal Luzynski
2019-01-15 18:22 ` Paul Eggert
2019-01-15 22:03 ` Rafal Luzynski
2019-01-15 17:09 ` Carlos O'Donell
2019-01-17 6:30 ` TAMUKI Shoichi [this message]
2019-01-17 6:29 ` TAMUKI Shoichi
2019-01-17 20:32 ` Rafal Luzynski
2019-01-18 13:58 ` TAMUKI Shoichi
2019-01-18 15:35 ` Rafal Luzynski
2019-01-15 20:09 ` Jochen Hein
2019-01-16 3:44 ` Siddhesh Poyarekar
2019-01-15 20:17 ` Carlos O'Donell
2019-01-16 3:47 ` Siddhesh Poyarekar
2019-01-22 3:28 ` Siddhesh Poyarekar
2019-01-22 3:52 ` H.J. Lu
2019-01-22 22:14 ` Joseph Myers
2019-01-22 4:21 ` Carlos O'Donell
2019-01-22 12:00 ` Florian Weimer
2019-01-22 13:06 ` Carlos O'Donell
2019-01-22 13:11 ` Szabolcs Nagy
2019-01-22 13:23 ` Carlos O'Donell
2019-01-22 15:17 ` Siddhesh Poyarekar
2019-01-22 15:48 ` Carlos O'Donell
2019-01-22 16:06 ` DCO or Copyright Assignment? Why not both Siddhesh Poyarekar
2019-01-28 13:00 ` Florian Weimer
2019-01-22 10:18 ` 2.29 freeze update: Last fortnight Rafal Luzynski
2019-01-16 3:13 ` H.J. Lu
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
List information: https://www.gnu.org/software/libc/involved.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=201901170630.AA04185@tamuki.linet.gr.jp \
--to=tamuki@linet.gr.jp \
--cc=carlos@redhat.com \
--cc=digitalfreak@lingonborough.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.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).