News for hackers. Stuff that matters.
Re:How to Write a Git Commit Message (2014) by data_hope on Thursday March 16, 2017 @06:20PM (#13889714)
I think you can do that in a merge commit, sort of.

The more I think about it, the stranger a strong aversion to rewriting commit history for clarity is. In university if I did some math / physics calculation, I would often start, and once I got somewhere, make a clean copy of the successful work to have a concise and revised version.

Re:How to Write a Git Commit Message (2014) by perfmode on Thursday March 16, 2017 @06:54PM (#13889901)
I am a firm believer that it's totally fine to rewrite history when working on a private branch that hasn't been pushed.
Re:How to Write a Git Commit Message (2014) by jononor on Thursday March 16, 2017 @08:00PM (#13890247)
Mostly fine to do it on a feature/PR branch also, in my opinion. If those become long-lived with multiple people touching them (where history rewrites become peoblematic) you are not integrating continuously enough.
Re:How to Write a Git Commit Message (2014) by cortesoft on Thursday March 16, 2017 @07:05PM (#13889956)
Not pushing private branches is risky though - you have no backup if something happens to your machine.