News for hackers. Stuff that matters.
Re:Lessons from PostgreSQL's Git transition by grammaton on Tuesday October 19, 2010 @09:36AM (#1807043)
Also keep in mind that a common work flow for tracking down an issue is to revert back to previous versions until you narrow down which one introduced the bug. In that case, you most certainly want fewer, cleaner commits. Narrowing a bug down to a commit that introduced four new features, fixed six bugs, and cleaned up a couple of dozen oopsies in the code base doesn't help you much.
Re:Lessons from PostgreSQL's Git transition by limmeau on Tuesday October 19, 2010 @09:46AM (#1807064)
Cleaner commits: agree. But the goal of fewer commits doesn't usually lead to fewer features per commit, rather more.
Re:Lessons from PostgreSQL's Git transition by alvherre on Tuesday October 19, 2010 @11:25AM (#1807420)
We strive to have exactly one feature or bugfix per commit. Squashing commits to a single one does not mean we mix stuff randomly.