public inbox for libc-alpha@sourceware.org
 help / color / mirror / Atom feed
From: Gianni Tedesco <gianni@scaramanga.co.uk>
To: Joseph Myers <joseph@codesourcery.com>, Paul Eggert <eggert@cs.ucla.edu>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH]: update leapseconds
Date: Mon, 19 Mar 2018 18:03:00 -0000	[thread overview]
Message-ID: <1521482626.12178.8.camel@scaramanga.co.uk> (raw)
In-Reply-To: <alpine.DEB.2.20.1803191659100.4537@digraph.polyomino.org.uk>

On Mon, 2018-03-19 at 17:00 +0000, Joseph Myers wrote:
> On Sun, 18 Mar 2018, Paul Eggert wrote:
> 
> > 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.
> 
> Maybe move them to e.g. timezone/test-sources?  (We already have 
> timezone/testdata for *binary* timezone files used as test inputs to
> the 
> timezone code, so it's probably a good idea to keep the different
> kinds of 
> test inputs separate.)

Yeah, well, it's also getting shipped as part of the binary
distribution, at least on ubuntu, so if it's just test data then that's
weird...

Gianni

  reply	other threads:[~2018-03-19 18:03 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
2018-03-19  7:54   ` Gianni Tedesco
2018-03-19 17:00   ` Joseph Myers
2018-03-19 18:03     ` Gianni Tedesco [this message]
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=1521482626.12178.8.camel@scaramanga.co.uk \
    --to=gianni@scaramanga.co.uk \
    --cc=eggert@cs.ucla.edu \
    --cc=joseph@codesourcery.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).