Open dilyanpalauzov opened 6 years ago
Hey there. It's been a while.
Your contribution efforts are appreciated. These are mostly fine patches, but is it at all possible we can get them as a github pull request? We're triaging some older bugs and the difference in workload between copying a bunch of text out of a colored git page vs just accepting a pull is non-trivial.
If not, we'll get to this eventually. It may just take a little longer.
I do not believe on any promises here.
https://github.com/trusteddomainproject/OpenDMARC/pull/119 fixes a bug, but is not considered yet and it does not matter how I provide the changes.
The changes I use are uploaded at https://mail.aegee.org/cgit/OpenDMARC/ . You can clone it and use any commit you like.
See my comments on #93 -- as for the documentation update, some of the updates here are good, others confuse me. For example, we like it when our manpages say what the default for a setting is, and while that makes manpages a bit longer, they compress.
I would need to cherry-pick this change a bit more to apply it all. Which I'm still happy to offer credit for. I'll take anything that makes the code more polished.
-Dan
The man page says:
Unless otherwise stated, Boolean values default to "false", integer values default to 0, and string and dataset values default to being undefined.
So either this text shall be removed, or the per flag text stating that the default is 0.
I'm not against having it in both places. Someone went to the trouble of writing it that way, and it's not misleading. Some people will skip through the manpage only looking for the field they're looking for and miss the subtle bit at the beginning.
That said, many of your other suggested fixes are great and I'm going to wind up cherry picking them in.