From: Andreas Schwab <schwab@suse.de>
To: Thorsten Kukuk via Libc-alpha <libc-alpha@sourceware.org>
Cc: Thorsten Kukuk <kukuk@suse.com>
Subject: Re: 64-bit time_t and __WORDSIZE_TIME64_COMPAT32
Date: Wed, 08 Feb 2023 11:27:25 +0100 [thread overview]
Message-ID: <mvmk00sv4du.fsf@suse.de> (raw)
In-Reply-To: <20230208102225.GA5543@suse.com> (Thorsten Kukuk via Libc-alpha's message of "Wed, 8 Feb 2023 11:22:25 +0100")
On Feb 08 2023, Thorsten Kukuk via Libc-alpha wrote:
> If they declare utmp and the file locations at their own, you need to
> modify them anyways. And if you do that, you can change them to use
> the official glibc API and not their own written one.
See utmpname.
--
Andreas Schwab, SUSE Labs, schwab@suse.de
GPG Key fingerprint = 0196 BAD8 1CE9 1970 F4BE 1748 E4D4 88E3 0EEA B9D7
"And now for something completely different."
next prev parent reply other threads:[~2023-02-08 10:27 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-08 9:18 Thorsten Kukuk
2023-02-08 10:06 ` Andreas Schwab
[not found] ` <0869a6f98f29405eb431f63db593c490@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:11 ` Thorsten Kukuk
2023-02-08 10:17 ` Andreas Schwab
[not found] ` <d2f1ee273add4af0868e07dc32542687@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:22 ` Thorsten Kukuk
2023-02-08 10:27 ` Andreas Schwab [this message]
[not found] ` <7485b79473614eaa994d3ea79c91629a@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-08 10:38 ` Thorsten Kukuk
2023-02-08 11:48 ` Adhemerval Zanella Netto
2023-02-14 8:24 ` Thorsten Kukuk
2023-02-14 8:59 ` Florian Weimer
[not found] ` <3230d2f8fa214c268cba52e699c14ae2@DB6PR04MB3255.eurprd04.prod.outlook.com>
2023-02-14 9:26 ` Thorsten Kukuk
2023-02-14 14:28 ` Adhemerval Zanella Netto
2023-02-16 13:59 ` Thorsten Kukuk
2023-04-11 11:40 ` Thorsten Kukuk
2023-04-11 13:23 ` Adhemerval Zanella Netto
2023-09-25 7:30 ` Thorsten Kukuk
2023-04-11 21:41 ` Paul Eggert
2023-04-12 6:55 ` Thorsten Kukuk
2023-04-12 23:36 ` Paul Eggert
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=mvmk00sv4du.fsf@suse.de \
--to=schwab@suse.de \
--cc=kukuk@suse.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).