| commit | 78ccd4419525562a2c9d2b7cebddba0914bde151 | |
| author | Santiago Torres <santiago@nyu.edu> | |
| Tue, 19 Apr 2016 17:47:19 +0000 (19 13:47 -0400) | ||
| committer | Junio C Hamano <gitster@pobox.com> | |
| Fri, 22 Apr 2016 21:06:46 +0000 (22 14:06 -0700) | ||
| tree | 34d4ab91fd6fff5cb45d60a908239ee882a6a6fb | treesnapshot (tar.gz zip) |
| parent | 20972f54d3f17007904cacb829c1feefb84a68dd | commitdiff |
verify-tag: prepare verify_tag for libification
The current interface of verify_tag() resolves reference names to SHA1,
however, the plan is to make this functionality public and the current
interface is cumbersome for callers: they are expected to supply the
textual representation of a sha1/refname. In many cases, this requires
them to turn the sha1 to hex representation, just to be converted back
inside verify_tag.
Add a SHA1 parameter to use instead of the name parameter, and rename
the name parameter to "name_to_report" for reporting purposes only.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Santiago Torres <santiago@nyu.edu>
Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
The current interface of verify_tag() resolves reference names to SHA1,
however, the plan is to make this functionality public and the current
interface is cumbersome for callers: they are expected to supply the
textual representation of a sha1/refname. In many cases, this requires
them to turn the sha1 to hex representation, just to be converted back
inside verify_tag.
Add a SHA1 parameter to use instead of the name parameter, and rename
the name parameter to "name_to_report" for reporting purposes only.
Helped-by: Junio C Hamano <gitster@pobox.com>
Signed-off-by: Santiago Torres <santiago@nyu.edu>
Reviewed-by: Eric Sunshine <sunshine@sunshineco.com>
Signed-off-by: Junio C Hamano <gitster@pobox.com>
| builtin/verify-tag.c | diffblobblamehistory |