unofficial mirror of notmuch@notmuchmail.org
 help / color / mirror / code / Atom feed
From: Jesse Rosenthal <jrosenthal@jhu.edu>
To: Tomi Ollila <tomi.ollila@iki.fi>, notmuch@notmuchmail.org
Subject: Re: [PATCH] emacs: derive correct timestamp in FCC unique name
Date: Thu, 14 Jun 2012 12:35:46 -0400	[thread overview]
Message-ID: <871ulhhmvx.fsf@jhu.edu> (raw)
In-Reply-To: <m2k3zamdo6.fsf@guru.guru-group.fi>

Hi, 

thanks for thinking this through.

On Thu, 14 Jun 2012, Tomi Ollila <tomi.ollila@iki.fi> wrote:
> Alternatives:
>
> 1) Use current patch, filenames will have extra '-' in 2038 on 32-bit
> systems.

Well, that assumes there is still the same arithmetic operations -- the
calendar issue will probably push them to either auto-convert to float
or use bignum. But still, assuming that in 2038, people are still on
32bit machines, it seems we should minimize the amount of things that
need to be fixed. 

So I agree that...

> 2) Drop 'timeid' and replace it with (float-time) in `format` call a few
> lines in original source after the patch context below -- No idea
> how (float-time) works on 32-bit systems after 2038.

is probably the best. They'll have to deal with their time_t (again,
assuming the unlikely existence of 32bit machines then) but this doesn't
depend on their arithemetic. 

I'll send a revision to this thread.

> I suggest option #2.
>
> Tomi

Thanks again,
Jesse

  reply	other threads:[~2012-06-14 17:35 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-13 20:01 [PATCH] emacs: derive correct timestamp in FCC unique name Jesse Rosenthal
2012-06-14  9:43 ` Tomi Ollila
2012-06-14 16:35   ` Jesse Rosenthal [this message]
2012-06-14 17:16 ` [PATCHv2] " Jesse Rosenthal
2012-06-14 19:04   ` Tomi Ollila
2012-06-22 10:45   ` David Bremner

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=871ulhhmvx.fsf@jhu.edu \
    --to=jrosenthal@jhu.edu \
    --cc=notmuch@notmuchmail.org \
    --cc=tomi.ollila@iki.fi \
    /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).