summaryrefslogtreecommitdiff
path: root/git-merge-one-file-script
diff options
context:
space:
mode:
authorLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-23 15:06:04 -0700
committerLinus Torvalds <torvalds@ppc970.osdl.org>2005-06-23 15:06:04 -0700
commitf97672225b3b1a2ca57cfc16f49239bed1efcd87 (patch)
tree859ea953f28818fc24eaa11108f1a90c98095ab3 /git-merge-one-file-script
parent180926636e47ecfe28d03cec493af75899994f0f (diff)
downloadgit-f97672225b3b1a2ca57cfc16f49239bed1efcd87.tar.gz
Add "git-patch-id" program to generate patch ID's.
A "patch ID" is nothing but a SHA1 of the diff associated with a patch, with whitespace and line numbers ignored. As such, it's "reasonably stable", but at the same time also reasonably unique, ie two patches that have the same "patch ID" are almost guaranteed to be the same thing. IOW, you can use this thing to look for likely duplicate commits.
Diffstat (limited to 'git-merge-one-file-script')
0 files changed, 0 insertions, 0 deletions