Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • What daxim said.

    Also, another option is, if no one else has worked on the branch but you, you could rebase it onto master to linearise the history, making it easier to read.

    But don’t squash entire branches in order to merge them. Focussed commits are easier to understand. They are also far more useful to git bisect.

    If you feel the need for good merge commit messages, just write them yourself, as hdp said.