On 2016-11-30 Wed 01:30 GMT-0800, Matt Armstrong <marmstrong@google.com> wrote:

> Hong Xu <hong@topbug.net> writes:
>
>> The function parse-time-string cannot parse ISO 8601 time string, e.g.,
>> 2005-04-07T22:13:13, which is pretty ubiquitous nowadays.
>> (parse-time-string 2005-04-07T22:13:13) returns a list full of nils.
>
> Hi Hong, parse-iso8601-time-string exists and can be used to parse ISO
> 8601 time strings.  It falls back to RFC 2822 style strings if that
> fails.  It would be nice if parse-time-string handled 8601 formt, but
> this has implications for current users.  I'll tag this bug a 'wishlist'
> in case others have opinions.

Thank you, that should have solved my problem!