summaryrefslogtreecommitdiff
path: root/arm
diff options
context:
space:
mode:
authorShawn O. Pearce <spearce@spearce.org>2006-12-23 03:44:00 -0500
committerJunio C Hamano <junkio@cox.net>2006-12-23 01:08:02 -0800
commitd9606e85cdf26b738786b5e5289bf8335656e95e (patch)
tree51486733e2a5461c01e9fcd91f36fb10e001c873 /arm
parent6be935115b4a3bfa9062875a569d4a018ac372e2 (diff)
downloadgit-d9606e85cdf26b738786b5e5289bf8335656e95e.tar.gz
Use extended SHA1 syntax in merge-recursive conflicts.
When we get a line-level conflict in merge-recursive and print out the two sides in the conflict hunk header and footer we should use the standard extended SHA1 syntax to specify the specific blob, as this allows the user to copy and paste the line right into 'git show' to view the complete version. Signed-off-by: Shawn O. Pearce <spearce@spearce.org> Signed-off-by: Junio C Hamano <junkio@cox.net>
Diffstat (limited to 'arm')
0 files changed, 0 insertions, 0 deletions