Brandon W Maister b553798f86 Support -0000 as a valid UTC tz in rfc2822 ... This is a time that is commonly set in some environments, and RFC 5322 explicitly clarifies that we should treat -0000 as UTC[1][2] when interpretting rfc2822. Fixes #102 [1]: https://github.com/chronotope/chrono/issues/102#issuecomment-557846931 [2]: https://tools.ietf.org/html/rfc5322#section-3.3		2019-11-30 16:48:35 -05:00
..
mod.rs	Replace all uses of `try!` with question mark	2019-11-23 19:18:08 -05:00
parse.rs	Support -0000 as a valid UTC tz in rfc2822	2019-11-30 16:48:35 -05:00
parsed.rs	Replace all uses of `try!` with question mark	2019-11-23 19:18:08 -05:00
scan.rs	Support -0000 as a valid UTC tz in rfc2822	2019-11-30 16:48:35 -05:00
strftime.rs	Use markdown footnotes in strftime docs	2019-11-22 11:30:10 -05:00