With the above output, we can now create a patch by running git diff > test_module_patch.patch This will create a file, test_module_patch.patch that has all of the outputs of the git diff command ...

Another is that they didn't have to learn how to use git commands. The downside is innumerable regressions as emailed commits overwrote previous code without a merge/diff/conflict process.

Git’s diff engine has a new heuristic for clarity in version 2.9. Diffs primarily show changes, additions, and deletions, King explained.