On Wed, Mar 17, 2010 at 12:58 AM, Kevin LaCoste <[email protected]> wrote: > Okay, I'm inclined to pretty strongly disagree with this. I would argue that > a commit message, by definition, should contain a message. Not code, not > ASCII art, but a descriptive message explaining the commit. If something > requires documentation, commit messages aren't really the appropriate place > for it. In other words, graphs belong in the documentation where people can > find them and code belongs in code files. > > Just to be sure I wasn't misunderstanding some part of the Git culture, I > took a peek at the Git repo, the Rails repo and a handful of Mac repos and > over the last 100 or so commits in each of them, found not a single example > of code or ASCII art. I also scanned through the entire history of GitX and > again, no examples.
Just look at stuff like http://github.com/git/git/commit/1830d9cb62772c0626297e4bb6e537664283ebfa There's a reason git log, gitk, gitx, github, git-gui and other tools use fixed-width fonts.
