From: Paul Eggert <eggert@cs.ucla.edu>
To: Albert ARIBAUD <albert.aribaud@3adev.fr>, Bruno Haible <bruno@clisp.org>
Cc: bug-gnulib@gnu.org, libc-alpha@sourceware.org
Subject: Re: [PATCH 1/1] Y2038: add function __difftime64
Date: Fri, 06 Jul 2018 22:54:00 -0000 [thread overview]
Message-ID: <5e5a5b90-91fd-fe01-70d8-82df2ee1b0b1@cs.ucla.edu> (raw)
In-Reply-To: <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.
next prev parent reply other threads:[~2018-07-06 22:54 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-06-20 12:14 [PATCH 0/1] Y2038 support batch 3 - difftime Albert ARIBAUD (3ADEV)
2018-06-20 12:14 ` [PATCH 1/1] Y2038: add function __difftime64 Albert ARIBAUD (3ADEV)
2018-06-20 19:29 ` Paul Eggert
2018-06-20 20:55 ` Albert ARIBAUD
2018-06-21 21:17 ` Paul Eggert
2018-06-25 22:32 ` Albert ARIBAUD
2018-06-25 23:56 ` Paul Eggert
2018-06-27 11:03 ` Albert ARIBAUD
2018-07-05 18:36 ` Albert ARIBAUD
2018-07-05 19:13 ` Zack Weinberg
2018-07-05 19:40 ` Paul Eggert
2018-07-05 20:38 ` Albert ARIBAUD
2018-07-05 21:17 ` Bruno Haible
2018-07-06 5:06 ` Albert ARIBAUD
2018-07-06 22:54 ` Paul Eggert [this message]
2018-07-06 22:40 ` Paul Eggert
2018-07-06 22:37 ` Paul Eggert
2018-07-17 20:40 ` Joseph Myers
2018-07-05 20:50 ` time_t in gnulib Bruno Haible
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=5e5a5b90-91fd-fe01-70d8-82df2ee1b0b1@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=albert.aribaud@3adev.fr \
--cc=bruno@clisp.org \
--cc=bug-gnulib@gnu.org \
--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).