onlyjob
The idea it to be able to produce binary identical builds by setting `SOURCE_DATE_EPOCH`. You can see that default behaviour is not changed unless `SOURCE_DATE_EPOCH` is set. When we re-build...
No worries. :)
I'm slightly disappointed that this improvement is still not merged (so it could not be incorporated into latest release 2.3.1). Is there any doubts or concerns regarding this change?
Unfortunately I have no time or skills to implement tests. Please feel free to take over this pull request and craft it to your preferences. Also it is worth noticing...
@mlewand, FYI Debian project typically uses the same license as upstream for most patches (unless otherwise is explicitly stated). This contribution is already license-clean.
So much dance around trivial pull request... :( What's wrong with you people?
I've rebased my commit. As far as I'm concerned it is ready to be merged...
I want to challenge the original (implied) statement that client-side CRC verification is bad. **Client data integrity checks are necessary**, even with performance impact, because _serving invalid data fast_ is...
No need to overreact so offensively, @anon314159. As I wrote, readers might easily think that _implied_ message of your complaint is that MooseFS client should not do CRC checks due...
Stop that "strawman" nonsense, @anon314159. My commentary is not an accusation or indictment. If we both agree that CRC checks in client are necessary, then what you are arguing about?...