aboutsummaryrefslogtreecommitdiff
path: root/project
diff options
context:
space:
mode:
authorAndrew Ash <andrew@andrewash.com>2014-02-12 23:23:06 -0800
committerPatrick Wendell <pwendell@gmail.com>2014-02-12 23:23:06 -0800
commit6ee0ad8fba660b48ef32dfa2f015b59cd5353a6e (patch)
treec0073d3de8004ef2dafd7ca1012a4ce398f0d787 /project
parent7fe7a55c820c6669c4ecccaa8599d05aec1b64be (diff)
downloadspark-6ee0ad8fba660b48ef32dfa2f015b59cd5353a6e.tar.gz
spark-6ee0ad8fba660b48ef32dfa2f015b59cd5353a6e.tar.bz2
spark-6ee0ad8fba660b48ef32dfa2f015b59cd5353a6e.zip
SPARK-1073 Keep GitHub pull request title as commit summary
The first line of a git commit message is the line that's used with many git tools as the most concise textual description of that message. The most common use that I see is in the short log, which is a one line per commit log of recent commits. This commit moves the line Merge pull request #%s from %s. Lower into the message to reserve the first line of the resulting commit for the much more important pull request title. http://tbaggery.com/2008/04/19/a-note-about-git-commit-messages.html Author: Andrew Ash <andrew@andrewash.com> Closes #574 from ash211/gh-pr-merge-title and squashes the following commits: b240823 [Andrew Ash] More merge_message improvements d2986db [Andrew Ash] Keep GitHub pull request title as commit summary
Diffstat (limited to 'project')
0 files changed, 0 insertions, 0 deletions