public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Paul Eggert <eggert@cs.ucla.edu>
To: Gianni Tedesco <gianni@scaramanga.co.uk>, libc-alpha@sourceware.org
Subject: Re: [PATCH]: update leapseconds
Date: Sun, 18 Mar 2018 23:59:00 -0000	[thread overview]
Message-ID: <e4cf5e94-f13d-d55a-6f6f-f26afa9307c0@cs.ucla.edu> (raw)
In-Reply-To: <1521318621.12178.2.camel@scaramanga.co.uk>

As I understand it, the leapseconds file (like most of the other files in the 
glibc timezone directory) is intended only for test data, and is not kept 
up-to-date. Perhaps this should be stated more clearly in the files' headers.

Another possibility would be to remove these files, as purposely out-of-date 
files cause confusion among glibc contributors.

  reply	other threads:[~2018-03-18 23:59 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-03-17 20:31 Gianni Tedesco
2018-03-18 23:59 ` Paul Eggert [this message]
2018-03-19  7:54   ` Gianni Tedesco
2018-03-19 17:00   ` Joseph Myers
2018-03-19 18:03     ` Gianni Tedesco
2018-03-19 18:08       ` Joseph Myers

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=e4cf5e94-f13d-d55a-6f6f-f26afa9307c0@cs.ucla.edu \
    --to=eggert@cs.ucla.edu \
    --cc=gianni@scaramanga.co.uk \
    --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).