Discussion on git commit requirements

From email by @gold2718

I still do not understand the logic of mashing together unrelated commits. The GitHub workflow is smoother and issues are easier to track (and debug) when made separately.
Using this issue and #20 as an example, say for the sake of argument that issue #20 introduced a change (AQP11 to AQPCONST) which is incompatible with my current work. Because there is no separate commit with issue #22 alone, I cannot easily use that while avoiding the #20 change as well.
Merging #20 as a separate PR with a couple of simple tests (already made by @nusbaume) would make no difference in the testing required to merge #20 and make a tag. On the other hand, it makes needed changes available more quickly.
If anyone still disagrees, please add some compelling arguments here.

Start by reading the discussion in this issue alongside issues #20 and #22, especially the examples about combining commits and the existing tests mentioned for #20. The issue does not identify files, an entry point, or a concrete completion condition, so the desired outcome must be agreed before implementation can begin.

Written by the indexing model from the issue text.