3 commits

Author	SHA1	Message	Date
Kai Ruemmler	9fabdedc0e	ignore new git-diff index header when computing patch ids ... Two else equal patches should not result in different checksums, only because they were applied to different versions of the file. Signed-off-by: Kai Ruemmler <kai.ruemmler@gmx.net> Signed-off-by: Junio C Hamano <junkio@cox.net>	2005-10-09 16:52:50 -07:00
Junio C Hamano	54c6870ebf	Typofix: usage strings fix. ... The *_usage strings should not start with "usage: ", since the usage() function gives its own. Signed-off-by: Junio C Hamano <junkio@cox.net>	2005-07-27 11:53:49 -07:00
Linus Torvalds	f97672225b	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.	2005-06-23 15:06:04 -07:00