Do all the things like ++ or -- rants, post your own rants, comment on others' rants and build your customized dev avatarSign Up
Voxera73522yNo, but a former colleague used to do that.
And in that commit you often found changes to a hundred files as he completely restructured something because he could not bother to ask when he did not understand if find what he needed, breaking things in a dozen places because he only ever tested that which he was working on, not other parts depending on it.
Its a warning that you have a growing problem that will one day explode and cause massive problems :/
Haxk20444482yMessages should always describe what you did. And always commit after every change you did.
Lets say we have variable that is NULL and crashes the kernel.
Commit would look like this: Net: Add value to variable "start" before using it.
And comment: This commit fixes Wifi issue we were having because variable start didnt have a value before using it and so it was NULL and crashed the kernel.