New Features
-
Support git default date format
This is the format output by default bygit log
or when using
--pretty=%ad
.The new git_date::time::format::GIT_DEFAULT format description may be used
to output date strings in this format. It is also now used by
git_date::parse() to accept date strings that may be in this format. -
Format git-style RFC 2822 date strings
Git outputs the day-of-month field as a non-padded number whereas strict
RFC 2822 date strings are supposed to use a zero-padded two-digit number.The new git_date::time::format::GIT_RFC2822 format description allows Time
to be formatted in git's RFC 2822 style. (Whereas the existing RFC2822
format description produces a strict RFC 2822 date string).
Bug Fixes
-
Stricter raw date parsing
The raw date parser (git_date::parse::function::parse_raw()) accepted some
inputs that it should not have. Specifically, it would accept:- Any character for the timezone offset's sign
-
Trailing, non-whitespace characters after the timezone offset
Other (BREAKING)
-
time::format::GIT_DEFAULT
->*::DEFAULT
and*::DEFAULT
->*::GITOXIDE
.
That way we properly indicate what we are doing and don't try to somewhat
sneakily suggest that the default for git dates is something else
due to personal preference.
Commit Statistics
- 9 commits contributed to the release over the course of 6 calendar days.
- 18 days passed between releases.
- 5 commits were understood as conventional.
- 0 issues like '(#ID)' were seen in commit messages
Commit Details
view details
- Uncategorized
- prepare changelogs prior to release (d679f5b)
time::format::GIT_DEFAULT
->*::DEFAULT
and*::DEFAULT
->*::GITOXIDE
. (41fc2bb)- Merge branch 'strict-raw-dates' (c65ce7e)
- Stricter raw date parsing (046af94)
- Merge branch 'issue-679' (a910d9e)
- refactor (26597b9)
- Support git default date format (4066ac7)
- Format git-style RFC 2822 date strings (8094351)
- Parse git-styled RFC 2822 date strings (dff0aa0)