git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: is it OK to PR just for code comment errors?


For typos in the documentation or javadocs feel free to open a PR.

I would leave code comments alone as long as the typo doesn't affect the clarity/semantics of the comment,
to not fragment the git history unnecessarily.

On 31.05.2018 11:40, makeyang wrote:
I am not sure if it is OK to PR just for code comment errors since I found
there is one when I am reading code



--
Sent from: http://apache-flink-user-mailing-list-archive.2336050.n4.nabble.com/