This is the mail archive of the
libc-alpha@sourceware.org
mailing list for the glibc project.
Re: [PATCH 1/1] Y2038: add function __difftime64
- From: Paul Eggert <eggert at cs dot ucla dot edu>
- To: Albert ARIBAUD <albert dot aribaud at 3adev dot fr>, Bruno Haible <bruno at clisp dot org>
- Cc: bug-gnulib at gnu dot org, libc-alpha at sourceware dot org
- Date: Fri, 6 Jul 2018 15:54:25 -0700
- Subject: Re: [PATCH 1/1] Y2038: add function __difftime64
- References: <20180620121427.25397-1-albert.aribaud@3adev.fr> <90246a4c-86cc-c191-8564-e6eea556fa13@cs.ucla.edu> <20180705223801.6e19c637@athena> <5612380.WK46iGFktE@omega> <20180706070547.068ecdfc@athena>
Albert ARIBAUD wrote:
Do code syncs from glibc to gnulib happen on new glibc releases?
It depends. Some of Gnulib syncs soon after a commit to glibc master. Other
parts of Gnulib sync more lackadasically. Glibc release boundaries don't matter
much.
Conversely, sometimes Glibc syncs files from Gnulib. Though this is rarer, it
happened a couple of days ago:
https://sourceware.org/git/?p=glibc.git;a=commit;h=eb04c21373e2a2885f3d52ff192b0499afe3c672
Come to think of it, we should update config/srclist.txt accordingly; I'll do
that shortly.
If they do, then my chick-and-egg problem remains
I don't quite know what you mean by chicken-and-egg problem, but it sounds like
we don't have the sort of blockage that you're worried about.