From: Joseph Myers <joseph@codesourcery.com>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
Elmar Stellnberger <estellnb@elstel.org>,
<libc-alpha@sourceware.org>
Subject: Re: time64 functions for glibc
Date: Wed, 23 Jun 2021 16:59:18 +0000 [thread overview]
Message-ID: <alpine.DEB.2.22.394.2106231655580.13671@digraph.polyomino.org.uk> (raw)
In-Reply-To: <e7f97130-580a-07a1-ec1d-16b55bd8e9a5@cs.ucla.edu>
On Tue, 22 Jun 2021, Paul Eggert wrote:
> -* Add support for 64 bit time_t for ABIs with defaults to 32 bit time_t.
> +* Add support for 64 bit time_t for ABIs with defaults currently unchanged.
I think the intended meaning of this was that "ABIs with defaults to 32
bit time_t" was a phrase describing those glibc configurations for which
support for 64-bit time_t was added (as opposed to those glibc
configurations already defaulting to 64-bit time_t in previous glibc
versions, for which nothing was changed), rather than "defaults to 32 bit
time_t" being a description of how the new feature behaves. I.e. this
change loses the information that many configurations already used 64-bit
time_t and so were unaffected by this change.
--
Joseph S. Myers
joseph@codesourcery.com
next prev parent reply other threads:[~2021-06-23 16:59 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-31 15:43 Elmar Stellnberger
2021-05-31 15:51 ` Paul Zimmermann
2021-05-31 16:01 ` Adhemerval Zanella
2021-05-31 18:46 ` Paul Eggert
2021-05-31 18:56 ` Florian Weimer
2021-05-31 19:08 ` Adhemerval Zanella
2021-05-31 19:16 ` Florian Weimer
2021-05-31 19:28 ` Adhemerval Zanella
2021-06-01 16:32 ` Elmar Stellnberger
2021-05-31 19:03 ` Adhemerval Zanella
2021-06-22 21:41 ` Paul Eggert
2021-06-23 13:29 ` Adhemerval Zanella
2021-06-23 16:59 ` Joseph Myers [this message]
2021-06-23 17:59 ` Paul Eggert
2021-06-24 17:37 ` 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=alpine.DEB.2.22.394.2106231655580.13671@digraph.polyomino.org.uk \
--to=joseph@codesourcery.com \
--cc=adhemerval.zanella@linaro.org \
--cc=eggert@cs.ucla.edu \
--cc=estellnb@elstel.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).