From: Peter Wang <novalazy@gmail.com>
To: David Bremner <david@tethera.net>
Cc: notmuch@notmuchmail.org
Subject: Re: timestamp overflows sprinter interface
Date: Sat, 8 Feb 2020 12:55:54 +1100 [thread overview]
Message-ID: <20200208125554.GD1447@kola.localdomain> (raw)
In-Reply-To: <87lfpjaivy.fsf@tethera.net>
On Mon, 03 Feb 2020 09:40:49 -0400, David Bremner <david@tethera.net> wrote:
> Peter Wang <novalazy@gmail.com> writes:
>
> > Hi,
> >
> > On a system where time_t is 64-bit and 'int' is a signed 32-bit integer
> > type, timestamps beyond some time in 2038 will be serialised to a
> > negative value.
>
> I admire your forward thinking!
Nah, someone reported an issue with my mail client when viewing a
message dated 09 Dec 2058.
>
> >
> > The simplest solution appears to be to change the type in the sprinter
> > method to int64_t:
> >
> > void (*integer)(struct sprinter *, int64_t);
> >
> > Any other suggestions?
>
> Since this is an internal API, I don't really see a big problem with
> doing this.
I've sent a patch.
Peter
prev parent reply other threads:[~2020-02-08 1:56 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-30 9:02 timestamp overflows sprinter interface Peter Wang
2020-02-03 13:40 ` David Bremner
2020-02-08 1:55 ` Peter Wang [this message]
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
List information: https://notmuchmail.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200208125554.GD1447@kola.localdomain \
--to=novalazy@gmail.com \
--cc=david@tethera.net \
--cc=notmuch@notmuchmail.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.
Code repositories for project(s) associated with this public inbox
https://yhetil.org/notmuch.git/
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).