public inbox for cygwin-patches@cygwin.com
 help / color / mirror / Atom feed
From: Jon Turney <jon.turney@dronecode.org.uk>
To: Brian Inglis <Brian.Inglis@SystematicSW.ab.ca>,
	Cygwin Patches <cygwin-patches@cygwin.com>
Subject: Re: [PATCH 0/3] strftime, strptime: add %i, %q, %v, tests; tweak %Z docs
Date: Thu, 15 Sep 2022 18:45:08 +0100	[thread overview]
Message-ID: <90d51419-b247-848d-6754-8ffd24792d31@dronecode.org.uk> (raw)
In-Reply-To: <20220914025236.54080-1-Brian.Inglis@SystematicSW.ab.ca>

On 14/09/2022 03:52, Brian Inglis wrote:
> [Please Reply All due to email issues]
> 
> newlib/libc/time/strftime.c(strftime): add %i, %q, %v, tests; tweak %Z docs
> newlib/libc/time/strptime.c(strptime_l): add %i, %q, %v
> winsup/cygwin/libc/strptime.cc(__strptime): add %i, %q, %v
> 
> %i year in century [00..99] Synonym for "%y". Non-POSIX extension. [tm_year]
> %q GNU quarter of the year (from `<<1>>' to `<<4>>') [tm_mon]
> %v OSX/Ruby VMS/Oracle date "%d-%b-%Y". Non-POSIX extension. [tm_mday, tm_mon, tm_year]
> add %i %q %v tests
> %Z clarify current time zone *abbreviation* not "name" [tm_isdst]

The newlib patches should go to the newlib list.

Do you have a reference for an OS supporting the %i extension?  I'm just 
curious if it specifies the same pivot year for strptime() as POSIX does 
for %y?


  parent reply	other threads:[~2022-09-15 17:45 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-14  2:52 Brian Inglis
2022-09-14  2:52 ` [PATCH 1/3] strftime.c(__strftime): " Brian Inglis
2022-09-14  2:52 ` [PATCH 2/3] strptime.c(strptime_l): add %i, %q, %v Brian Inglis
2022-09-14  2:52 ` [PATCH 3/3] strptime.cc(__strptime): " Brian Inglis
2022-09-15 17:45 ` Jon Turney [this message]
2022-09-15 19:52   ` [PATCH 0/3] strftime, strptime: add %i, %q, %v, tests; tweak %Z docs Brian Inglis

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=90d51419-b247-848d-6754-8ffd24792d31@dronecode.org.uk \
    --to=jon.turney@dronecode.org.uk \
    --cc=Brian.Inglis@SystematicSW.ab.ca \
    --cc=cygwin-patches@cygwin.com \
    /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).