From: Andreas Schwab <schwab@suse.de>
To: Paul Eggert <eggert@cs.ucla.edu>
Cc: "Daniel P. Berrangé" <berrange@redhat.com>,
"Demi Marie Obenour" <demiobenour@gmail.com>,
"Eric Blake" <eblake@redhat.com>, "Sam James" <sam@gentoo.org>,
"Carlos O'Donell via Libc-alpha" <libc-alpha@sourceware.org>,
autoconf@gnu.org, c-std-porting@lists.linux.dev,
"Zack Weinberg" <zack@owlfolio.org>,
"David Seifert" <soap@gentoo.org>,
"Gentoo Toolchain" <toolchain@gentoo.org>,
"Arsen Arsenović" <arsen@aarsen.me>,
rjones@redhat.com
Subject: Re: On time64 and Large File Support
Date: Thu, 02 Mar 2023 11:38:27 +0100 [thread overview]
Message-ID: <mvmv8jjl9p8.fsf@suse.de> (raw)
In-Reply-To: <7253e4c5-0f36-e725-f180-624f8887bf08@cs.ucla.edu> (Paul Eggert's message of "Thu, 2 Mar 2023 02:28:28 -0800")
On Mär 02 2023, Paul Eggert wrote:
> Fifteen years from now we'll be saying the same thing about
> _TIME_BITS. There will be some pain in the meantime, just as there was
> with the _FILE_OFFSET_BITS transition, something I lived through and was
> not too happy about either.
There is a huge difference between them: time_t has a flag day, off_t
doesn't. You can still run with 32-bit off_t today and have everything
working.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-03-02 10:38 UTC|newest]
Thread overview: 75+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-11 8:38 On time64 and Large File Support Sam James
2022-11-11 9:16 ` Paul Eggert
2022-11-11 9:19 ` Sam James
2022-11-11 23:48 ` Joseph Myers
2022-11-11 9:19 ` Florian Weimer
2022-11-11 9:27 ` Sam James
2022-11-11 11:38 ` Florian Weimer
2022-11-11 20:12 ` Paul Eggert
2022-11-12 2:20 ` Zack Weinberg
2022-11-12 3:57 ` Sam James
2022-11-12 14:16 ` Zack Weinberg
2022-11-12 17:41 ` Paul Eggert
2022-11-12 18:50 ` Bruno Haible
2022-11-12 19:15 ` Paul Eggert
2022-11-12 20:23 ` Wookey
2022-11-12 20:54 ` Russ Allbery
2022-11-12 21:31 ` Paul Eggert
[not found] ` <951fc967-042c-4978-bd78-8bc4c8706b18@app.fastmail.com>
2022-11-13 5:11 ` Zack Weinberg
2022-11-15 5:06 ` Sam James
2022-12-25 19:19 ` Paul Eggert
2022-12-29 4:02 ` Zack Weinberg
2022-12-30 22:12 ` Paul Eggert
2022-12-30 22:20 ` Sam James
2023-01-20 9:56 ` Paul Eggert
2023-02-02 6:43 ` Sam James
2023-02-02 23:15 ` time for Autoconf 2.72 (was: On time64 and Large File Support) Paul Eggert
2023-02-02 23:17 ` Zack Weinberg
2023-02-03 5:49 ` Sam James
2023-02-03 12:43 ` time for Autoconf 2.72 Bruno Haible
[not found] ` <CAObJKZp2CCRR46-X9NYaRES7eDCVyoJ0xv=u4aSG2KeQv4vtjA@mail.gmail.com>
2023-02-27 2:30 ` time for Autoconf 2.72 (was: On time64 and Large File Support) Sam James
2023-03-17 23:47 ` Sam James
2023-03-18 0:59 ` Paul Eggert
2023-03-18 2:08 ` Jim Meyering
2023-03-18 2:52 ` Paul Eggert
2023-03-19 0:30 ` Jim Meyering
2023-03-19 0:57 ` Sam James
2022-11-15 5:09 ` On time64 and Large File Support Sam James
2022-11-12 18:19 ` Paul Eggert
2022-11-11 9:40 ` Andreas K. Huettel
2022-11-11 11:30 ` Florian Weimer
2022-11-11 19:01 ` Andreas K. Huettel
2022-11-11 19:28 ` Palmer Dabbelt
2022-11-11 9:46 ` Paul Eggert
2022-11-11 11:22 ` Florian Weimer
2022-11-11 19:56 ` Paul Eggert
2022-11-12 4:20 ` Wookey
2022-11-12 4:28 ` Sam James
2022-11-12 4:56 ` Wookey
2022-11-12 4:59 ` Sam James
2022-11-12 18:33 ` Paul Eggert
2022-11-14 8:39 ` Adam Sampson
2022-11-14 11:47 ` Florian Weimer
2022-11-14 20:26 ` Arsen Arsenović
2022-11-14 20:52 ` Florian Weimer
2022-11-15 7:39 ` Arsen Arsenović
2022-11-11 10:25 ` Richard Purdie
2023-03-01 22:38 ` Eric Blake
2023-03-02 0:29 ` Demi Marie Obenour
2023-03-02 9:04 ` Daniel P. Berrangé
2023-03-02 10:28 ` Paul Eggert
2023-03-02 10:38 ` Andreas Schwab [this message]
2023-03-03 5:46 ` Paul Eggert
2023-03-06 8:58 ` Andreas Schwab
2023-03-06 10:19 ` Florian Weimer
2023-03-02 11:02 ` Richard W.M. Jones
2023-03-02 12:17 ` Bruno Haible
2023-03-02 13:24 ` Daniel P. Berrangé
2023-03-03 3:30 ` Wookey
2023-03-03 5:50 ` Paul Eggert
2023-03-03 14:01 ` Wookey
2023-03-03 14:14 ` Daniel P. Berrangé
2023-03-03 23:21 ` Arsen Arsenović
2023-03-03 11:49 ` Florian Weimer
2023-03-03 12:39 ` Richard W.M. Jones
2023-03-02 8:30 ` Richard W.M. Jones
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=mvmv8jjl9p8.fsf@suse.de \
--to=schwab@suse.de \
--cc=arsen@aarsen.me \
--cc=autoconf@gnu.org \
--cc=berrange@redhat.com \
--cc=c-std-porting@lists.linux.dev \
--cc=demiobenour@gmail.com \
--cc=eblake@redhat.com \
--cc=eggert@cs.ucla.edu \
--cc=libc-alpha@sourceware.org \
--cc=rjones@redhat.com \
--cc=sam@gentoo.org \
--cc=soap@gentoo.org \
--cc=toolchain@gentoo.org \
--cc=zack@owlfolio.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.