From: Andreas Schwab <schwab@suse.de>
To: DJ Delorie via Libc-alpha <libc-alpha@sourceware.org>
Cc: Adhemerval Zanella <adhemerval.zanella@linaro.org>,
DJ Delorie <dj@redhat.com>,
zev@bewilderbeest.net, wayne.tung@ui.com
Subject: Re: [PATCH 2/3] nscd: Use 64 bit time_t on libc nscd routines (BZ# 29402)
Date: Thu, 27 Oct 2022 14:48:07 +0200 [thread overview]
Message-ID: <mvm1qqta0vs.fsf@suse.de> (raw)
In-Reply-To: <xnwn8m5kiu.fsf@greed.delorie.com> (DJ Delorie via Libc-alpha's message of "Wed, 26 Oct 2022 17:42:49 -0400")
On Okt 26 2022, DJ Delorie via Libc-alpha wrote:
> Wait... does this mean that the format of the nscd cache changed at some
> point and we didn't flag it as an externally visible ABI change?
nscd_time_t has always been a 64-bit type.
--
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:[~2022-10-27 12:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-26 19:04 [PATCH 0/3] Fixing missing 64 bit time_t usages Adhemerval Zanella
2022-10-26 19:04 ` [PATCH 1/3] nis: Build libnsl with 64 bit time_t Adhemerval Zanella
2022-12-09 4:30 ` DJ Delorie
2022-12-09 4:31 ` DJ Delorie
2022-12-09 14:35 ` Adhemerval Zanella Netto
2022-10-26 19:04 ` [PATCH 2/3] nscd: Use 64 bit time_t on libc nscd routines (BZ# 29402) Adhemerval Zanella
2022-10-26 21:42 ` DJ Delorie
2022-10-27 12:31 ` Adhemerval Zanella Netto
2022-10-27 12:48 ` Andreas Schwab [this message]
2022-12-09 4:30 ` DJ Delorie
2022-10-26 19:04 ` [PATCH 3/3] time: Use 64 bit time on tzfile Adhemerval Zanella
2022-12-09 4:31 ` DJ Delorie
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=mvm1qqta0vs.fsf@suse.de \
--to=schwab@suse.de \
--cc=adhemerval.zanella@linaro.org \
--cc=dj@redhat.com \
--cc=libc-alpha@sourceware.org \
--cc=wayne.tung@ui.com \
--cc=zev@bewilderbeest.net \
/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).