Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

My only complaint is, I write long commit messages, since the commit messages are shown in single line, it overflows the viewing area. so, if there are linebreaks for longer git messages, it would be awesome.


Git best practices say the first line in your commit message should be no more than 50 characters. Subsequent lines should be wrapped at 80 characters. See http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa...


I've been using multiple lines in my log messages, but didn't know about second blank line.

I tried as per pilgrim689's comment, Now everything is fine with --oneline argument.

Thanks.


Long commit messages are good, but if you want them to display nicely in short logs, enter them the way git and linux kernel commit messages do:

<short 1-liner explaining change>

<blank line>

<paragraph with commit details>

then `git log --oneline` displays the 1-liners perfectly.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: