Eli Zaretskii <eliz@gnu.org> writes:

>> Cc: 65450@debbugs.gnu.org
>> From: Ihor Radchenko <yantar92@posteo.net>
>> Date: Wed, 23 Aug 2023 06:40:39 +0000
>> 
>> "Dr. Arne Babenhauserheide" <arne_bab@web.de> writes:
>> 
>> > This is kind of suspicious, because 2038 is when the year 2038 problem
>> > looms. Is Emacs vulnerable?
>> 
>> See `org-read-date-force-compatible-dates'. Emacs is vulnerable on some
>> platforms, AFAIR. Also, see https://yhetil.org/emacs-devel/8735gaqm6i.fsf@localhost/

Thank you for the reference!

>> After the last discussion I did not see it safe to flip the default
>> value of `org-read-date-force-compatible-dates'.
>
> So this doesn't seem to be an Emacs bug, or a bug at all, but rather a
> feature of Org?  If so, we should close this bug, I guess?

Can Emacs add a fallback mechanism so org can stop working around the
issue?

Best wishes,
Arne
-- 
Unpolitisch sein
heißt politisch sein,
ohne es zu merken.
draketo.de