From: Paul Eggert <eggert@cs.ucla.edu>
To: Florian Weimer <fweimer@redhat.com>
Cc: libc-alpha@sourceware.org
Subject: Re: [PATCH v3 2/3] login: structs utmp, utmpx, lastlog _TIME_BITS independence (bug 30701)
Date: Wed, 17 Apr 2024 14:14:39 -0700 [thread overview]
Message-ID: <d7d6fed9-28d4-43fb-830a-f45d7a2ee070@cs.ucla.edu> (raw)
In-Reply-To: <87h6g3nfe0.fsf@oldenburg.str.redhat.com>
On 4/15/24 02:28, Florian Weimer wrote:
> I can implement it that way, but I'm not sure if it's
> worth the complexity. This would only benefit obsolescent applications
> that are recompiled.
You're right, it would benefit only those old applications, and only
when they are built in an obsolescent way (i.e., with 32-bit time_t).
If it's greater complexity to support obsolescent builds I suppose
you're right, and let's not bother.
The old applications I help maintain are all using _TIME_BITS=64 on
these platforms, so they won't be built in an obsolescent way and won't
care about this.
next prev parent reply other threads:[~2024-04-17 21:14 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-04-10 6:45 [PATCH v3 0/3] login: Use unsigned 32-bit types for seconds-since-epoch Florian Weimer
2024-04-10 6:45 ` [PATCH v3 1/3] login: Check default sizes of structs utmp, utmpx, lastlog Florian Weimer
2024-04-12 16:14 ` Adhemerval Zanella Netto
2024-04-10 6:45 ` [PATCH v3 2/3] login: structs utmp, utmpx, lastlog _TIME_BITS independence (bug 30701) Florian Weimer
2024-04-12 16:15 ` Adhemerval Zanella Netto
2024-04-12 21:23 ` Paul Eggert
2024-04-15 9:28 ` Florian Weimer
2024-04-17 21:14 ` Paul Eggert [this message]
2024-04-10 6:45 ` [PATCH v3 3/3] login: Use unsigned 32-bit types for seconds-since-epoch Florian Weimer
2024-04-12 16:19 ` Adhemerval Zanella Netto
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=d7d6fed9-28d4-43fb-830a-f45d7a2ee070@cs.ucla.edu \
--to=eggert@cs.ucla.edu \
--cc=fweimer@redhat.com \
--cc=libc-alpha@sourceware.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 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).