Christian CouderFrom: =?UTF-8?q?Nguy=E1=BB=85n=20Th=C3=A1i=20Ng=E1=BB=8Dc=20Duy?= <pclouds@gmail.com>
Commit 0e87c36 (object: call "check_sha1_signature" with the replacement sha1) changed the first argument passed to parse_object_buffer() from "sha1" to "repl". With that change, the returned obj pointer has the replacement SHA1 in obj->sha1, not the original one.
But when using lookup_commit() and then parse_commit() on a commit, we get an object pointer with the original sha1, but the commit content comes from the replacement commit.
So the result we get from using parse_object() is different from the we get from using lookup_commit() followed by parse_commit().
It looks much simpler and safer to fix this inconsistency by passing "sha1" to parse_object_bufer() instead of "repl".
The commit comment should be used to tell the the replacement commit is replacing another commit and why. So it should be easy to see that we have a replacement commit instead of an original one.
And it is not a problem if the content of the commit is not consistent with the sha1 as cat-file piped to hash-object can be used to see the difference.
Signed-off-by: Christian Couder <chriscool@tuxfamily.org> --- Since no one resent the original patch with an improved commit message, here is my try.
object.c | 2 +- 1 files changed, 1 insertions(+), 1 deletions(-)
Show changes to object.c +1 −1
diff --git a/object.c b/object.c index 277b3dd..7adfda7 100644 --- a/object.c +++ b/object.c @@ -199,7 +199,7 @@ struct object *parse_object(const unsigned char *sha1) return NULL; } - obj = parse_object_buffer(repl, type, size, buffer, &eaten); + obj = parse_object_buffer(sha1, type, size, buffer, &eaten); if (!eaten) free(buffer); return obj;
-- 1.7.2.2.417.g10a17
