On Sat, May 11, 2019 at 10:42 AM Cy Schubert <cy.schub...@cschubert.com> wrote:
> In message <201905111637.x4bgbawj032...@gndrsh.dnsmgr.net>, "Rodney W. > Grimes" > writes: > > > On Sat, 2019-05-11 at 14:22 +0000, Xin LI wrote: > > > > Author: delphij > > > > Date: Sat May 11 14:22:21 2019 > > > > New Revision: 347488 > > > > URL: https://svnweb.freebsd.org/changeset/base/347488 > > > > > > > > Log: > > > > Update leap-seconds to leap-seconds.3757622400. > > > > > > > > > > For future reference: it's a bit better to get this file from NIST [*] > > > than from USNO. The USNO boilerplate is full of typos, and USNO > > > incorrectly adjusts the "last update date" metadata every time they > > > change the expiration date of the file. That's not correct... as the > > > boilerplate itself states, that field is only supposed to be updated > > > when new leap seconds are added to the file. > > > > I would be very happy if that information would end up in the > > top of, or next to the leap-seconds file so that it was followed > > in the future, rather than being folk lore. > > > > Thanks, > > Rod > > Leap seconds hasn't been updated upstream since 2017. USNO updates the > file when they last paid attention to the file by not updating it. NIST > only updates the file when there is indeed an update, that being Ian's > point. > Yeah, obviously I somehow misread the commit message of r320256. I can do a follow commit to fix it tonight but if you have some time please feel free to fix it now. Cheers, _______________________________________________ svn-src-head@freebsd.org mailing list https://lists.freebsd.org/mailman/listinfo/svn-src-head To unsubscribe, send any mail to "svn-src-head-unsubscr...@freebsd.org"
