author | Junio C Hamano <junkio@cox.net> | |
Mon, 5 Feb 2007 05:49:05 +0000 (21:49 -0800) | ||
committer | Junio C Hamano <junkio@cox.net> | |
Mon, 5 Feb 2007 22:55:11 +0000 (14:55 -0800) | ||
commit | 005f85d9ae95c44d8c6ecf61364642fbcaf49dd2 | |
tree | 7e5fc9be65d54b8f55d970493cc45b935a341586 | tree | snapshot |
parent | d66b37bb19ff7a347ba4ccbcdc11b00772518b57 | commit | diff |
Use pretend_sha1_file() in git-blame and git-merge-recursive.
git-merge-recursive wants an null tree as the fake merge base
while producing the merge result tree. The null tree does not
have to be written out in the object store as it won't be part
of the result, and it is a prime example for using the new
pretend_sha1_file() function.
git-blame needs to register an arbitrary data to in-core index
while annotating a working tree file (or standard input), but
git-blame is a read-only application and the user of it could
even lack the privilege to write into the object store; it is
another good example for pretend_sha1_file().
Signed-off-by: Junio C Hamano <junkio@cox.net>
git-merge-recursive wants an null tree as the fake merge base
while producing the merge result tree. The null tree does not
have to be written out in the object store as it won't be part
of the result, and it is a prime example for using the new
pretend_sha1_file() function.
git-blame needs to register an arbitrary data to in-core index
while annotating a working tree file (or standard input), but
git-blame is a read-only application and the user of it could
even lack the privilege to write into the object store; it is
another good example for pretend_sha1_file().
Signed-off-by: Junio C Hamano <junkio@cox.net>
builtin-blame.c | diff | blob | history | |
merge-recursive.c | diff | blob | history |