Am 2017-05-15 um 17:19 schrieb Gary Gregory:
On Mon, May 15, 2017 at 8:04 AM, Michael Osipov <micha...@apache.org> wrote:
Am 2017-05-15 um 16:36 schrieb Oleg Kalnichevski:
On Mon, 2017-05-15 at 16:18 +0200, Michael Osipov wrote:
...
Am 2017-05-15 um 16:00 schrieb Oleg Kalnichevski:
What benefit do you have if it is hard to follow the code paths? How
much is "good" code worth if you don't have proper documentation?
Even
if you have to constantly clean up their mess just like mom did?
I see the log as a documentation of our work. At the end, good code
does
not help if it cannot be properly located by others. I still think
that
all committers should help the RM to do as little as possible and
not
more than necessary.
Michael
Michael,
It is the same deal as with the decision on an logging API.
Please put together a short statement what our Git commit policies
should be (probably in Wiki), ask people to comment / complain, then
copy the statement into an email and call a vote.
I actually did: https://mail-archives.apache.o
rg/mod_mbox/hc-dev/201705.mbox/%3C010661f8-4e15-01af-6a5a-
971baa1348ca%40apache.org%3E
and some people agreed, including you and Gary.
Anyway, here is the wiki page: https://wiki.apache.org/HttpCo
mponents/GitPoliciesAndPractices
"Policies" and "Practices"? What's the difference? I do not see two
sections on the page ;-) Can we take down the corporate-speak down a notch
and go for "Git Guidelines"?
Makes sense, done!
Thank you.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@hc.apache.org
For additional commands, e-mail: dev-h...@hc.apache.org
