Home
last modified time | relevance | path

Searched refs:RFC2822 (Results 1 – 8 of 8) sorted by relevance

/external/rust/crates/chrono/src/format/
Dparse.rs439 &RFC2822 => try_consume!(parse_rfc2822(parsed, s)), in parse_internal()
827 parse(&mut parsed, date, [Item::Fixed(Fixed::RFC2822)].iter())?; in test_rfc2822()
832 dt.format_with_items([Item::Fixed(Fixed::RFC2822)].iter()).to_string() in test_rfc2822()
Dmod.rs225 RFC2822, enumerator
640 RFC2822 => in format_inner()
/external/rust/crates/chrono/src/
Ddatetime.rs348 const ITEMS: &'static [Item<'static>] = &[Item::Fixed(Fixed::RFC2822)]; in parse_from_rfc2822()
400 const ITEMS: &'static [Item<'static>] = &[Item::Fixed(Fixed::RFC2822)]; in to_rfc2822()
/external/rust/crates/chrono/
DCHANGELOG.md245 * RFC2822 allows times to not include the second (@upsuper)
/external/python/cpython2/Misc/NEWS.d/
D2.7.1rc1.rst675 email.utils.parsedate now returns RFC2822 compliant four character years
/external/pcre/dist2/testdata/
Dtestinput15899 # definitions in RFC2822, without any of the obsolete features. The addition of
Dtestoutput19453 # definitions in RFC2822, without any of the obsolete features. The addition of
/external/python/cpython3/Misc/
DHISTORY9353 functions, allowing for round tripping of RFC2822 format dates.
12453 - Issue #1194222: email.utils.parsedate now returns RFC2822 compliant four