Eric Engestrom <e...@engestrom.ch> writes:
> Before, new tags had their names shown twice:
> * [new tag] v4.5-rc6 -> v4.5-rc6
>
> Instead, show the hash of the commit pointed to:
> * [new tag] v4.5-rc6 -> fc77dbd
>
> Signed-off-by: Eric Engestrom <e...@engestrom.ch>
The report from update-local-refs is meant to show what "local"
names the updated ref has, i.e. what names you can refer the result
as. If you fetched v4.5-rc6, the output tells you that you can
refer to it as v4.5-rc6 in your local repository.
Technically, you can also refer to the tag as fc77dbd, but I do not
see why a user would want to.
In addition, if I did:
$ git fetch $his_repository 'refs/tags/*:refs/tags/his/*'
I'd see his 'v1.0' tag locally stored as 'his/v1.0', and that is
what is shown in the output as
* [new tag] v1.0 -> his/v1.0
so that I know I can refer to his v1.0 as "his/v1.0", to
differenticate from the tag I happen to have created as v1.0 in my
local repository.
So, why is this change an improvement?
> ---
>
> This is my first dive into git's code, so it's likely I'm not doing things
> right. The first candidate for that is the literal `7`, which should probably
> be a variable, but I couldn't find what I should use instead.
>
> I'd be happy to fix this for a v2 :]
>
> Cheers,
> Eric
>
>
> builtin/fetch.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/builtin/fetch.c b/builtin/fetch.c
> index e4639d8..93b2145 100644
> --- a/builtin/fetch.c
> +++ b/builtin/fetch.c
> @@ -515,6 +515,7 @@ static int update_local_ref(struct ref *ref,
> if (starts_with(name, "refs/tags/")) {
> msg = "storing tag";
> what = _("[new tag]");
> + pretty_ref = find_unique_abbrev(ref->new_oid.hash, 7);
> } else if (starts_with(name, "refs/heads/")) {
> msg = "storing head";
> what = _("[new branch]");
--
To unsubscribe from this list: send the line "unsubscribe git" in
the body of a message to majord...@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
