Paul Dicker

@cppcoffee Is there a not-too-difficult way for me to test chrono on openwrt?

Okay, I can reproduce it. ``` docker import http://downloads.openwrt.org/attitude_adjustment/12.09/x86/generic/openwrt-x86-generic-rootfs.tar.gz openwrt-x86-generic-rootfs rustup target add x86_64-unknown-linux-musl docker run -v $(pwd)/target/x86_64-unknown-linux-musl:/target -i openwrt-x86-generic-rootfs /target/debug/deps/chrono-f094327353343c38 ``` Our test suite fails with: ``` failures: ----...

The docker image has no timezone files and `/etc/TZ` is a dangling pointer. Maybe timezone support has to be installed first?

To solve this we need to know what OpenWRT does that is different from regular Linux distributions. Can someone provide the following information? - Contents of `TZ` variable - What...

I have to admit all the test failures when i was working on the parsing of `%:z`, `%::z` etc were highly annoying…. but also quite useful and I was thankful...

@jtmoon79 The last commit in https://github.com/pitdicker/chrono/commits/parse_padding is what I was thinking it would take to work with whitespace in combination with padding specifiers. Just putting it in here to spare...

I would like to see at least the tests from https://github.com/chronotope/chrono/pull/807 back on the 0.4.x branch. I don't think that part would be any problem, and it would go a...

I don't feel like we have huge gaps in our coverage of parsing. More tests is not per se better, as we have to maintain and fix merge conflicts in...

> I entirely forgot about this PR! 🙀 > Let me get back to you, hopefully within a few weeks rather than months. No worries :smile:. > IMO #1112 is...

I have removed the part from this PR to error on unused fields. Now it should accept strictly more strings as valid when parsing, so it should be good for...