From: Stanley Lieber <sl@stanleylieber.com>
To: 9front@9front.org
Subject: Re: [9front] date -t vs rfc3339 i which is correct:
Date: Tue, 10 Dec 2019 14:48:09 -0500 [thread overview]
Message-ID: <A123A33B-9FA9-44F5-807B-7D3C7661BD3A@stanleylieber.com> (raw)
In-Reply-To: <361ED9A9F4CE301DE0E938744EF73C41@eigenstate.org>
i don’t recall what the original need was.
werc’s blagh app generates an atom feed, which needs rfc3339 dates, and an rss feed, which needs rfc2822 dates. 9front’s date -m is good for rfc2822.
but since werc is targeted at the lowest common denominator p9p, i implemented 9front date -m and -t as rc functions in werclib.rc. i noticed the rfc3339 vs iso-8601 discrepancy when atom.tpl still failed to validate atom feeds. so, werclib.rc/^fn ndate now has flags -a for rfc3339, -t for iso-8601, and -m for rfc2822. i kept -t for now (it’s just an echo statement) in case somebody needs it later.
sl
prev parent reply other threads:[~2019-12-10 19:48 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-10 19:17 cinap_lenrek
2019-12-10 19:34 ` ori
2019-12-10 19:48 ` Stanley Lieber [this message]
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=A123A33B-9FA9-44F5-807B-7D3C7661BD3A@stanleylieber.com \
--to=sl@stanleylieber.com \
--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).