public inbox for libc-locales@sourceware.org
 help / color / mirror / Atom feed
From: Zack Weinberg <zackw@panix.com>
To: Keld Simonsen <keld@keldix.com>
Cc: GNU C Library <libc-alpha@sourceware.org>, libc-locales@sourceware.org
Subject: Re: Removing locale timezone information
Date: Wed, 12 Aug 2015 21:07:00 -0000	[thread overview]
Message-ID: <CAKCAbMj3X-G10=RVZaBoV8oZbC7tzYDaDtvNyf1WmijkihFAvQ@mail.gmail.com> (raw)
In-Reply-To: <20150812140837.GA23436@www5.open-std.org>

On Wed, Aug 12, 2015 at 10:08 AM,  <keld@keldix.com> wrote:
> My impression is that timezone changes are normally announced in due time
> so that they can be included in normal glibc release schedule, which
> I think is about twice a year, but irregulary. I have not been down into
> the data, tho.

Sadly, as pointed out by others, this is not so.

Keld, would your use cases be satisfied if each glibc locale (for
which this makes sense) specified a default *Olsen* timezone?  I think
that might be a way to get what you want while avoiding the problems
everyone else is bringing up.

zw

  parent reply	other threads:[~2015-08-12 21:07 UTC|newest]

Thread overview: 47+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-03 15:57 Marko Myllynen
2015-06-03 21:33 ` Paul Eggert
2015-06-03 21:33 ` keld
2015-06-05  8:28   ` Marko Myllynen
2015-08-06 21:45     ` keld
2015-08-06 21:45       ` pinskia
2015-08-06 21:46         ` keld
2015-08-07  2:33         ` Rich Felker
2015-08-07  0:45       ` Mike Frysinger
2015-08-09 21:12         ` keld
2015-08-07 21:49       ` Paul Eggert
2015-08-09 21:12         ` keld
2015-08-09 21:12           ` Paul Eggert
     [not found]             ` <20150812140837.GA23436@www5.open-std.org>
2015-08-12 21:07               ` Zack Weinberg [this message]
2015-08-12 23:13                 ` Keld Simonsen
2015-08-12 23:13                   ` Allan McRae
2015-08-12 21:07               ` Allan McRae
2015-08-12 21:07               ` Paul Eggert
2015-08-12 21:07               ` Andreas Schwab
2015-06-12 14:05 ` [PATCH] Remove " Marko Myllynen
2015-08-05  9:07   ` Mike Frysinger
2015-08-05 11:51     ` keld
2015-08-05 11:51       ` keld
2015-08-05 10:53         ` Mike Frysinger
2015-08-05 11:52           ` keld
2015-08-05 12:39             ` Andreas Schwab
2015-08-05 13:09               ` keld
2015-08-05 13:33             ` Mike Frysinger
2015-08-05 15:56               ` Keld Simonsen
2015-08-05 16:30                 ` Joseph Myers
2015-08-06 21:46                   ` Keld Simonsen
2015-08-06 21:46                     ` Joseph Myers
2015-08-06 21:46                     ` Andreas Schwab
2015-08-06 21:46                       ` Zack Weinberg
2015-08-06  2:53                 ` Mike Frysinger
2015-08-05 11:52         ` Andreas Schwab
2015-08-05 11:52           ` keld
2015-08-05 12:30             ` Andreas Schwab
2015-08-05 13:03               ` keld
2015-08-05 16:30         ` Paul Eggert
2015-08-06  2:56           ` Mike Frysinger
2015-08-06 17:13             ` keld
2015-08-06 17:13               ` Paul Eggert
2015-08-06 17:22                 ` keld
2015-08-06 17:14               ` pinskia
2015-08-06 17:25                 ` keld
2015-08-06 17:14           ` keld

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='CAKCAbMj3X-G10=RVZaBoV8oZbC7tzYDaDtvNyf1WmijkihFAvQ@mail.gmail.com' \
    --to=zackw@panix.com \
    --cc=keld@keldix.com \
    --cc=libc-alpha@sourceware.org \
    --cc=libc-locales@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).