1 Aug
2022
1 Aug
'22
9:05 a.m.
On Mon Aug 1 08:57:20 2022 +0000, Bernhard K��lbl wrote:
It's generally wanted to only have "atomic" changes per commit, so it's easier to bisect if an issue arises in the future. So put everything into a commit that is introducing an independent feature change / new feature. So yeah, put both implementations in separate commits as well. Regarding the tests, you can mark stuff, which is going to be fixed by a future commit, with `todo_wine`. So commit tests first and the impl afterwards.
Oh, and the prefix for any commit is usually the folder where you do commit to. So instead of `cabinet.dll: Do foobar.` it's just `cabinet: Do foobar.` One exception are headers, where it's `include/foo.h: Do foobar.`