public inbox for linux-man@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert Elz <kre@munnari.OZ.AU>
To: Alejandro Colomar <alx@kernel.org>
Cc: Andrew Josey <ajosey@opengroup.org>,
	Geoff Clare <gwc@opengroup.org>,
	Vincent Lefevre <vincent@vinc17.net>,
	Xi Ruoyao <xry111@xry111.site>, Paul Eggert <eggert@cs.ucla.edu>,
	libc-alpha@sourceware.org, DJ Delorie <dj@redhat.com>,
	linux-man@vger.kernel.org, carlos@redhat.com,
	Jens Gustedt <jens.gustedt@inria.fr>,
	austin-group-l@opengroup.org
Subject: Re: [PATCH v3] ctime.3: EXAMPLES: Add example program
Date: Sat, 24 Aug 2024 01:46:05 +0700	[thread overview]
Message-ID: <9649.1724438765@jacaranda.noi.kre.to> (raw)
In-Reply-To: <cb65drmcb6cotrz6rzkfuwg5aod2jta4ma6f6cds4pouk5tjdj@6wl6iwby2isi>

    Date:        Fri, 23 Aug 2024 19:48:09 +0200
    From:        Alejandro Colomar <alx@kernel.org>
    Message-ID:  <cb65drmcb6cotrz6rzkfuwg5aod2jta4ma6f6cds4pouk5tjdj@6wl6iwby2isi>

I kind of suspect there has been some discussion I am not privy to
preceding this, so if anything I add here seems redundant, or whatever,
that's why.

  | (Although I'm not sure if that mailing list is open.  maybe it rejects
  |  mail from this account.  Please anyone bounce it if you find that it
  |  doesn't reach the list.)

Same here.  I am fairly sure (since I have received no recent messages)
that I got dropped from the austin list during a period when munnari.oz.au
was reachable only via IPv6 (something of an experiment, though the
original reasoning was different).    It appears that the austin-group
mailing list is only able to transmit mail via IPv4.   Shame.

Also note that I removed "Robert C. Seacord" <rcseacord@gmail.com>
from the recipient list, as gmail continue to refuse to receive mail
from munnari - there was no point attempting that one.   Someone can
forward if that seems called for.


  | > and which implementations have been checked.
  | Robert, Geoff, Andrew, can you please clarify?

Me, no, sorry, that is something from the linux world I think.

I actually have no idea whether our implementation (Paul might be
able to guess, since this is unlikely to have been changed from tzcode)
whether our implementation alters tm_wday in various failure cases or
not.

  | Robert, Geoff, Andrew, can you please clarify where is the discussion
  | that led to the following change?:

There were a lot of discussions about mtime() - lots of it on the list,
some of it in the mantis defect report database (associated with more than
one bug), and more about strftime("%s") which is almost the same thing.

Sorry, I can't point you at anything in particular which led to that.

  | You could argue with them that there's no way to test for errors other
  | than this method,

That's probably a reasonable summary of the rationale.

  | I guess if a weekday was ever added,

If there's anything about the management of times less likely to happen
than that one, I cannot imagine it.   Weeks with fewer days are possible,
in bizarre circumstances (like when Gregorian time became standard) but
not ones with more.   It would be more likely that the concept of a week,
and weekday names, would be eliminated, than a new day be added.

Adding months would be a far more likely thing to happen - after all,
that's happened before.

Of course, if the whole way of measuring time were to be changed, then
almost anything might appear as a replacement.   mktime() wouldn't apply.

kre



  reply	other threads:[~2024-08-23 19:01 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-23 23:11 [PATCH v4] ctime.3: Document how to detect invalid or ambiguous times Alejandro Colomar
     [not found] ` <xned6jlywd.fsf@greed.delorie.com>
2024-08-22 23:49   ` [PATCH v3] ctime.3: EXAMPLES: Add example program Alejandro Colomar
2024-08-23  4:57     ` Paul Eggert
2024-08-23  7:02       ` Alejandro Colomar
2024-08-23  7:26         ` Xi Ruoyao
2024-08-23  7:57           ` Vincent Lefevre
2024-08-23 12:28           ` Alejandro Colomar
2024-08-23 12:28             ` Xi Ruoyao
2024-08-23 12:53             ` Vincent Lefevre
2024-08-23 13:12               ` Alejandro Colomar
2024-08-23 13:54                 ` Vincent Lefevre
2024-08-23 14:18                   ` Alejandro Colomar
2024-08-23 15:26                     ` Vincent Lefevre
2024-08-23 17:48                       ` Alejandro Colomar
2024-08-23 18:46                         ` Robert Elz [this message]
2024-08-23 19:08                         ` Paul Eggert
2024-08-23 20:09                           ` Hans Åberg
2024-08-23 20:34                           ` Alejandro Colomar
2024-08-23 14:04                 ` Brian Inglis
2024-08-23 14:25                   ` Alejandro Colomar
2024-08-23 18:31                     ` Brian Inglis
2024-08-23 20:27                       ` Alejandro Colomar
2024-08-24  8:46   ` [PATCH v5] ctime.3: Document how to detect invalid or ambiguous times Alejandro Colomar
2024-08-25 18:33     ` Alejandro Colomar
2024-08-30 11:09     ` [PATCH v6] ctime.3: EXAMPLES: " Alejandro Colomar

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=9649.1724438765@jacaranda.noi.kre.to \
    --to=kre@munnari.oz.au \
    --cc=ajosey@opengroup.org \
    --cc=alx@kernel.org \
    --cc=austin-group-l@opengroup.org \
    --cc=carlos@redhat.com \
    --cc=dj@redhat.com \
    --cc=eggert@cs.ucla.edu \
    --cc=gwc@opengroup.org \
    --cc=jens.gustedt@inria.fr \
    --cc=libc-alpha@sourceware.org \
    --cc=linux-man@vger.kernel.org \
    --cc=vincent@vinc17.net \
    --cc=xry111@xry111.site \
    /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