| commit | c8762c30df5b5c0a2a91e14e77cfc94b459d089b | |
| author | brian m. carlson <sandals@crustytoothpaste.net> | |
| Mon, 2 Oct 2023 02:40:20 +0000 (1 21:40 -0500) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Mon, 2 Oct 2023 21:57:39 +0000 (2 14:57 -0700) | ||
| tree | aa2474cb31cecc289f38045251cc20e7dc0ccf80 | treesnapshot (tar.gz zip) |
| parent | 33a14e81ae0673f8b3f7cf85168c7c573fa2fb58 | commitdiff |
object-file-convert: convert tag objects when writing
When writing a tag object in a repository with both SHA-1 and SHA-256,
we'll need to convert our commit objects so that we can write the hash
values for both into the repository. To do so, let's add a function to
convert tag objects.
Note that signatures for tag objects in the current algorithm trail the
message, and those for the alternate algorithm are in headers.
Therefore, we parse the tag object for both a trailing signature and a
header and then, when writing the other format, swap the two around.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
When writing a tag object in a repository with both SHA-1 and SHA-256,
we'll need to convert our commit objects so that we can write the hash
values for both into the repository. To do so, let's add a function to
convert tag objects.
Note that signatures for tag objects in the current algorithm trail the
message, and those for the alternate algorithm are in headers.
Therefore, we parse the tag object for both a trailing signature and a
header and then, when writing the other format, swap the two around.
Signed-off-by: brian m. carlson <sandals@crustytoothpaste.net>
Signed-off-by: Eric W. Biederman <ebiederm@xmission.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| object-file-convert.c | diffblobblamehistory |