News for hackers. Stuff that matters.
Re:GitHub - Shiny new commit styles by lautis on Tuesday September 06, 2011 @04:36PM (#2967190)
Numbers in commit messages don't really make any sense. I don't understand what value they might have. The narrative of your codebase is hard to follow when large number of your commits don't have any message explaining what you've done.

I like to commit (quite) frequently when working on something, but later I feel that work-in-progress commits are just hindrance. When looking at project history after two year, I'll be glad if there is a single, larger commit "implemented feature x". Rebase is your friend.

Re:GitHub - Shiny new commit styles by akkartik on Tuesday September 06, 2011 @05:04PM (#2967295)
"Numbers in commit messages don't really make any sense. I don't understand what value they might have."

I like to refer to 'commit 347' rather than 'commit a3bh'. There's an implicit sense of how old a commit is.

Re:GitHub - Shiny new commit styles by Peaker on Wednesday September 07, 2011 @01:49AM (#2968534)
Then if you later decide to shuffle the order of the commits, squash, or do other interesting things, you run into GWBASIC line numbering problems.
Re:GitHub - Shiny new commit styles by akkartik on Wednesday September 07, 2011 @02:00AM (#2968556)
I find I'm far less likely to need to insert commits than I was to insert lines in GWBASIC.