aboutsummaryrefslogtreecommitdiff
path: root/Makefile
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 /Makefile
parent180926636e47ecfe28d03cec493af75899994f0f (diff)
downloadgit-f97672225b3b1a2ca57cfc16f49239bed1efcd87.tar.gz
git-f97672225b3b1a2ca57cfc16f49239bed1efcd87.tar.xz
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 'Makefile')
-rw-r--r--Makefile3
1 files changed, 2 insertions, 1 deletions
diff --git a/Makefile b/Makefile
index e3405dc3a..fd5c80f75 100644
--- a/Makefile
+++ b/Makefile
@@ -35,7 +35,7 @@ PROG= git-update-cache git-diff-files git-init-db git-write-tree \
git-http-pull git-ssh-push git-ssh-pull git-rev-list git-mktag \
git-diff-helper git-tar-tree git-local-pull git-write-blob \
git-get-tar-commit-id git-mkdelta git-apply git-stripspace \
- git-cvs2git git-diff-stages git-rev-parse
+ git-cvs2git git-diff-stages git-rev-parse git-patch-id
all: $(PROG)
@@ -121,6 +121,7 @@ git-stripspace: stripspace.c
git-cvs2git: cvs2git.c
git-diff-stages: diff-stages.c
git-rev-parse: rev-parse.c
+git-patch-id: patch-id.c
git-http-pull: LIBS += -lcurl
git-rev-list: LIBS += -lssl