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
..
format	Support -0000 as a valid UTC tz in rfc2822	2019-11-30 16:48:35 -05:00
naive	Replace all uses of `try!` with question mark	2019-11-23 19:18:08 -05:00
offset	Replace all uses of `try!` with question mark	2019-11-23 19:18:08 -05:00
date.rs	Accept Borrow<Item> as items	2019-11-23 23:34:59 +01:00
datetime.rs	Support -0000 as a valid UTC tz in rfc2822	2019-11-30 16:48:35 -05:00
div.rs	Use no_std-compatible num dependencies	2018-02-23 00:07:16 -08:00
lib.rs	Remove unused constant, deny(dead_code)	2019-11-23 19:58:20 -05:00
oldtime.rs	Replace all uses of `try!` with question mark	2019-11-23 19:18:08 -05:00
round.rs	Implement Support for no_std	2019-09-07 12:12:49 +02:00