From: Rafal Luzynski <digitalfreak@lingonborough.com>
To: TAMUKI Shoichi <tamuki@linet.gr.jp>, libc-alpha@sourceware.org
Cc: Siddhesh Poyarekar <siddhesh@gotplt.org>,
Carlos O'Donell <carlos@redhat.com>,
Joseph Myers <joseph@codesourcery.com>
Subject: Re: 2.29 freeze update: Last fortnight
Date: Fri, 18 Jan 2019 16:35:13 +0100 (CET) [thread overview]
Message-ID: <1487907897.434044.1547825713484@poczta.nazwa.pl> (raw)
In-Reply-To: <201901181358.AA04193@tamuki.linet.gr.jp>
18.01.2019 14:58 TAMUKI Shoichi <tamuki@linet.gr.jp> wrote:
> [...]
> I checked carefully and confirmed that using yr_spec as a simple int
> is no problem. In addition, I also found that "yr_spec = 0" after
> __strftime_internal function call is unnecessary. Based on this, I
> will fix the next patch.
Yes, please prepare the next patch with that change. It will be less
confusing, easier to understand and maintain, and less error prone.
Thank you.
Regards,
Rafal
next prev parent reply other threads:[~2019-01-18 15:36 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
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 [this message]
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=1487907897.434044.1547825713484@poczta.nazwa.pl \
--to=digitalfreak@lingonborough.com \
--cc=carlos@redhat.com \
--cc=joseph@codesourcery.com \
--cc=libc-alpha@sourceware.org \
--cc=siddhesh@gotplt.org \
--cc=tamuki@linet.gr.jp \
/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).