Get the latest tech news
When to split patches for PostgreSQL
In my previous article on how to submit patches by email for PostgreSQL, I skipped over whether patches should be split up. Let’s discuss that now.
If you work on a larger project, you will inevitably find stuff you want to clean up, weird formatting, confusing comments, ancient coding style, etc. The latter is probably easiest: If you write an email, “here is some cleanup I did while working on something else”, together with a really clean and obvious patch, someone can quickly pick that up and review it or commit it. (Note, if you have several different kinds of cleanups, such as formatting changes, comment typos, etc., it’s probably also good to split those into separate patches attached to the same email.)
Or read this on Hacker News