[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: encode-time vs decode-time
From: |
Eli Zaretskii |
Subject: |
Re: encode-time vs decode-time |
Date: |
Sat, 17 Aug 2019 11:16:33 +0300 |
> From: Paul Eggert <address@hidden>
> Date: Sat, 17 Aug 2019 00:54:07 -0700
> Cc: Eli Zaretskii <address@hidden>, address@hidden, address@hidden
>
> The POSIX tradition is to call these timestamps "broken-down time", and that
> is
> what glibc calls them too. How about if we use that name instead? It would
> help
> to be more consistent with other GNU code.
"Broken-down time" will replace "decoded time", I presume? I think
I'm okay with that, but what will we use instead of "encoded time"
then?
- Re: encode-time vs decode-time, (continued)
- Re: encode-time vs decode-time, Eli Zaretskii, 2019/08/06
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/06
- Re: encode-time vs decode-time, Eli Zaretskii, 2019/08/06
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/06
- Re: encode-time vs decode-time, Stefan Monnier, 2019/08/06
- Re: encode-time vs decode-time, Eli Zaretskii, 2019/08/07
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/08/11
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/08/07
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time,
Eli Zaretskii <=
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Lars Ingebrigtsen, 2019/08/17
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Stefan Monnier, 2019/08/17
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/17
- Re: encode-time vs decode-time, Stefan Monnier, 2019/08/19
- Re: encode-time vs decode-time, Adam Porter, 2019/08/21
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/21
- Re: encode-time vs decode-time, Adam Porter, 2019/08/26
- Re: encode-time vs decode-time, Paul Eggert, 2019/08/26