News for hackers. Stuff that matters.
Re:A multi-purpose EDITOR variable by pilgrim689 on Saturday March 30, 2013 @08:34PM (#5467189)
depends. for small commits, a one-liner suffices. For large commits, merge commits, etc., or for repos that require you to sign-off on the commit or whatnot, a one-liner followed by a blank line and then a nice paragraph or bullet-point list is necessary. "launching a full editor" is hardly a problem with emacsclient or vi[m]
Re:A multi-purpose EDITOR variable by jordibunster on Sunday March 31, 2013 @04:59AM (#5468146)
The smaller the commit, the more likely that it needs a proper explanation of why it was made.

When you find a commit from two years ago that changes a constant from -1 to -2, and the commit message says "constant change", or "bugfix in floobers" you're left with no context.