Top all-time · #1472
tbaggery
Personal blog · tbaggery.comprogrammingwriting
tbaggery is a personal blog at tbaggery.com about programming and writing. Since 2010, 51 different Hacker News readers have linked it 56 times, most often “A Note About Git Commit Messages”. The last post was in 2011, but the archive is still widely read.
Most-linked posts?
- A Note About Git Commit Messages26 people · 26 mentions · first linked 2010-04-28
- A Note About Git Commit Messages15 people · 19 mentions · first linked 2018-02-28
- Effortless Ctags with Git (function indexing etc, for your editor)5 people · 5 mentions · first linked 2011-08-09
- Is tpope asleep?2 people · 2 mentions · first linked 2011-03-10
What Hacker News says?
Ok, found this, linked by Mr. Torvalds http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Linus Torvalds won't do github pull requests”Submitted A Note About Git Commit Messages as a story · 104 points
HN discussionAccording to http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... (linked in one of the comments in the github discussion) it is for consistency with the commit message generated by 'git merge' and the like.
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Linus Torvalds won't do github pull requests”Submitted Smack a Ho.st - A localhost domain as a story · 36 points
HN discussion72 characters per line is a common standard for git commit messages. If you use vim, the syntax highlighting will nudge you to exactly that number. https://tbaggery.com/2008/04/19/a-note-about-git-commit-mess...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Cosmopolitan v3.5”Submitted Effortless Ctags with Git (function indexing etc, for your editor) as a story · 6 points
HN discussionGit 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...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “A better git log”Submitted Bundle While You Git as a story · 5 points
HN discussionIn my usage, the story is for myself first and foremost. Telling the story helps keep me organized and helps me remember what I've done and where I'm going. I don't need to know that I fixed a typo in a comment, I need to know what the changes are overall doing. Sometimes I go down a dead end, reverse out, and leave a comment about why a different approach would be a dead end. I (and others) don't need a record of t…
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “The Theatre of Pull Requests and Code Review”Submitted A Note About Git Commit Messages as a story · 4 points
HN discussionIt appears to originate with Tim Pope: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... Reading between the lines, it seems that the 50 character limit is to accommodate commands like "git log --pretty=oneline" and "git rebase --interactive" on an 80 column terminal. He also recommends 72 columns for any subsequent text because git makes a left margin of 4 characters and it looks balanced if you also…
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Commit messages are not titles”Submitted A Note About Git Commit Messages as a story · 3 points
HN discussionWhen using Git's mail features -- remember, not everyone uses GitHub -- the first line of a commit is a subject line. It's good practice to just think of it that way. If you write sentences in your subject lines in e-mail, I guess, that's up to you. Don't take it from me, read the Tim Pope counterpoint, with eight extremely good reasons for concise subjects in the closing paragraph: http://tbaggery.com/2008/04/19/a-…
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Commit messages are not titles”Submitted A Note About Git Commit Messages (2008) as a story · 2 points
HN discussionThat's unfortunate, and I think your experience reflects most places I've worked at too. It doesn't have to be that way though; technical leadership on a team can choose to care about this kind of thing and coach their colleagues into caring more about writing communicative commit messages. To any technical leaders reading this comment, I encourage you to choose to care about this :) Here's the post I always share o…
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Using Git commit message templates to write better commit messages”Submitted Tbaggery – A Note About Git Commit Messages as a story · 2 points
HN discussionMy personal favorites on the topic: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... https://robots.thoughtbot.com/5-useful-tips-for-a-better-com...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “A README maturity model”Submitted Tbaggery – Effortless Ctags with Git as a story · 2 points
HN discussionhttps://tbaggery.com/2008/04/19/a-note-about-git-commit-mess... (2008)
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Rob Pike on good commit messages (2014)”Submitted Effortless Ctags with Git (2011) as a story · 2 points
HN discussionI don't like the idea of your gg function, but I add files to the index using git add -p exclusively since it gives me a chance to review my changes as I'm adding them, as well as let's me ensure I split up different logical changes into separate commits. Likewise, I think git commit -m encourages lazy git commit messages (see: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... ) Mostly because this hel…
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Git tips from the trenches”Submitted Tbaggery - Effortless Ctags with Git as a story · 2 points
HN discussionThis is a good post about readable commit messages: http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Linus: please write good git commit messages”Submitted Is tpope asleep? as a story · 2 points
HN discussionhttp://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... gives a good description.
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Huffshell: You probably type too much.”Submitted A Note About Git Commit Messages (2008) as a story · 1 points
HN discussiongreat. next up: a well-written & concise guide on writing proper commit messages. could be based on http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa... and http://robots.thoughtbot.com/5-useful-tips-for-a-better-comm...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Contributing to Open Source on GitHub”Submitted A Note About Git Commit Messages as a story · 1 points
HN discussionThis is probably more on point--"A Note About Git Commit Messages” http://tbaggery.com/2008/04/19/a-note-about-git-commit-messa...
Comment linking /2008/04/19/a-note-about-git-commit-messages.html
on “Version control: best practices”Submitted A Note About Git Commit Messages as a story · 1 points
HN discussion
