From: ori@eigenstate.org
To: ori@eigenstate.org, 9front@9front.org
Subject: Re: [9front] libc: date handling improvements
Date: Sat, 13 Jun 2020 12:40:08 -0700 [thread overview]
Message-ID: <364F2C1F2CDA34BA1E40FA14CDBA8767@eigenstate.org> (raw)
In-Reply-To: <AE583BF0F480F9D2360D51764C6A37CC@eigenstate.org>
> I implemented libdate -- but the right place to put
> it is in libc, replacing our ctime and gmtime apis.
>
> Follow ups will replace seconds(1), upas time parsing
> code, and whatever other instances of hand rolled date
> parsing and formatting can be found.
>
> Here's a patch that does this. Testing appreciated,
> and follow ups that I haven't done yet would also be
> great :)
>
Committed -- please let me know if you notice any
breakage.
next prev parent reply other threads:[~2020-06-13 19:40 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-05-31 3:39 ori
2020-05-31 4:57 ` [9front] " ori
2020-06-06 20:56 ` ori
2020-06-13 19:40 ` ori [this message]
2020-06-15 6:02 ` ori
2020-06-15 6:03 ori
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=364F2C1F2CDA34BA1E40FA14CDBA8767@eigenstate.org \
--to=ori@eigenstate.org \
--cc=9front@9front.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 NNTP newsgroup(s).