From: Carlos O'Donell <carlos@redhat.com>
To: Paul Eggert <eggert@cs.ucla.edu>,
Hans-Peter Nilsson <hp@axis.com>,
libc-alpha@sourceware.org
Cc: Christopher.Wong@axis.com
Subject: Re: [PATCH v2] timezone: handle truncated timezones from tzcode-2021d and later (BZ #28707)
Date: Fri, 17 Dec 2021 09:24:20 -0500 [thread overview]
Message-ID: <fd5119e4-74b5-ef8a-5d34-517928530b46@redhat.com> (raw)
In-Reply-To: <949e52bb-05a6-5ae6-edd1-37382384a554@cs.ucla.edu>
On 12/16/21 21:51, Paul Eggert wrote:
> Thanks for the patch. The basic idea looks right, but:
Paul,
What is the impact of this for all of the downstream distributions?
I would like to avoid having every distribution scrambling to patch
glibc to handle new tdata binary files, but if we need to do this
patch I would like to get it into all of the active release branches.
--
Cheers,
Carlos.
next prev parent reply other threads:[~2021-12-17 14:24 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-06 14:50 [PATCH] time: Remove assert in reading of tz file Christopher Wong
2021-12-06 15:10 ` Florian Weimer
2021-12-06 15:16 ` Christopher Wong
2021-12-17 0:57 ` [PATCH v2] timezone: handle truncated timezones from tzcode-2021d and later (BZ #28707) Hans-Peter Nilsson
2021-12-17 2:51 ` Paul Eggert
2021-12-17 14:05 ` Carlos O'Donell
2021-12-17 20:33 ` Hans-Peter Nilsson
2021-12-17 14:24 ` Carlos O'Donell [this message]
2021-12-17 17:57 ` Paul Eggert
2021-12-17 18:11 ` Hans-Peter Nilsson
2021-12-17 18:40 ` Paul Eggert
2021-12-17 20:36 ` [PATCH v3 0/2] timezone: BZ #28707 Hans-Peter Nilsson
2021-12-17 22:22 ` Paul Eggert
2021-12-29 0:50 ` Hans-Peter Nilsson
2021-12-29 23:12 ` Adhemerval Zanella
2021-12-17 20:38 ` [PATCH v3 1/2] timezone: handle truncated timezones from tzcode-2021d and later (BZ #28707) Hans-Peter Nilsson
2021-12-17 20:45 ` [PATCH v3 2/2] timezone: test-case for BZ #28707 Hans-Peter Nilsson
2021-12-17 20:51 ` Hans-Peter Nilsson
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=fd5119e4-74b5-ef8a-5d34-517928530b46@redhat.com \
--to=carlos@redhat.com \
--cc=Christopher.Wong@axis.com \
--cc=eggert@cs.ucla.edu \
--cc=hp@axis.com \
--cc=libc-alpha@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).