unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: <tomas@tuxteam.de>
To: Achim Gratz <Stromeko@nexgo.de>
Cc: emacs-devel@gnu.org
Subject: Re: Represent NTP's origin time
Date: Sat, 17 Apr 2021 17:27:36 +0200	[thread overview]
Message-ID: <20210417152736.GA3748@tuxteam.de> (raw)
In-Reply-To: <87tuo5x8od.fsf@Rainer.invalid>

[-- Attachment #1: Type: text/plain, Size: 1334 bytes --]

On Sat, Apr 17, 2021 at 04:55:14PM +0200, Achim Gratz wrote:
> tomas@tuxteam.de writes:
> > I replied (or so I thought) "in kind". A better reply would have
> > been: Emacs supports 32 bit platforms. Unless ending 32 bit
> > support is in the near-future, it'd be a good idea to think about
> > how to support a wider (possibly 64 bit) time_t even on a 32 bit
> > Emacs.
> 
> The support for 64bit time_t on 32bit platforms is quite old by now
> actually, but it hasn't seen as much uptake as initially envisioned for
> whatever reasons.  So in effect those platforms have announced their EOL
> and you should move off them.
> 
> > The *BSDs and Linux (beyond kernel 5.6ish) do support 64 bit time_t
> > in their 32 bit variants: perhaps this is an orientation.
> 
> I have no 32bit system left that can run a modern enough Linux kernel
> and doesn't also support 64bit, so once I update those will not be 32bit
> anymore.

Again. The fact that *you* haven't doesn't mean that others are
in the same boat. A maintainer's job involves exactly that kind
of deliberation :)

(I'd bet that Stefan's hardware is still 32 bit :)

So basically it reduces to whether the Emacs project wants to
support 32 bit systems (currently, the answer seems to be "yes")
and what to do about time_t when yes.

Cheers
 - t

[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2021-04-17 15:27 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-04-15  4:00 Represent NTP's origin time Stefan Monnier
2021-04-15  8:06 ` Andreas Schwab
2021-04-15  8:22   ` Gregory Heytings
2021-04-15  8:27 ` Ulrich Mueller
2021-04-15  8:30   ` Eli Zaretskii
2021-04-15 12:40   ` Stefan Monnier
2021-04-15 12:56     ` Andreas Schwab
2021-04-15 13:39       ` Stefan Monnier
2021-04-15 13:41     ` Ulrich Mueller
2021-04-15 13:44       ` Stefan Monnier
2021-04-15 14:06     ` Gregory Heytings
2021-04-15 14:51       ` Stefan Monnier
2021-04-15 19:12 ` Achim Gratz
2021-04-16  7:06   ` tomas
2021-04-17  3:53   ` Richard Stallman
2021-04-17  7:30     ` tomas
2021-04-17 13:44   ` Achim Gratz
2021-04-17 14:09     ` tomas
2021-04-17 14:23       ` Stefan Monnier
2021-04-17 14:55       ` Achim Gratz
2021-04-17 15:27         ` tomas [this message]
2021-04-17 16:20           ` Achim Gratz
2021-04-17 16:54           ` [OFFTOPIC] " Stefan Monnier
2021-04-17 20:00             ` tomas
2021-04-17 20:31               ` Stefan Monnier

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://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20210417152736.GA3748@tuxteam.de \
    --to=tomas@tuxteam.de \
    --cc=Stromeko@nexgo.de \
    --cc=emacs-devel@gnu.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://git.savannah.gnu.org/cgit/emacs.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).