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

I often review commit logs of my teams, especially while we are tracking down problems or I'm making sure the release notes capture everything.

There has to be a balance between this and "WIP"; I'm imagining trying to page through the commit log to see what changed when every 1 line change has a 35 line commit associated with it.



That’s the beauty of it, the first 50 characters of the first line (IIRC) will be shown as a summary, and this one summarizes 35 lines in seven words.


I believe there's a standard format for this.

The first line is the title, then there's a description.

These heavy descriptions of commits, are used quite heavily in linux kernel dev


Would `git log --oneline` not help?




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

Search: