KF5 Tags tag tags, not objects

[Stephen Kelly]

If you look in gitk at karchive (or any other repo), you can see that commit 
d2e7c78c94e6 is tagged with both v5.21.0-rc2 and v5.21.0.

If you click on the v5.21.0-rc2 tag, you can see that it tags the commit. 
That is the usual thing to do.


Tag: v5.21.0-rc2
object d2e7c78c94e629a60bcff7b5c1abaf43e8ac7d75
type commit   ##### << GOOD
tag v5.21.0-rc2
tagger l10n daemon script <scripty at kde.org> 1459716237 +0000

It says it tags the d2e7c78c94e629a60bcff7b5c1abaf43e8ac7d75 object, which 
is the commit.

However, click on the v5.21.0 to see that it tags a tag

Tag: v5.21.0
object 6122c6149595f5f915c99ca4c7bd82e6415f1482
type tag     ##### << BAD
tag v5.21.0
tagger l10n daemon script <scripty at kde.org> 1460196978 +0000

Create tag for 5.21.0

We can see what the 6122c6149595 object is:

$ git cat-file -p 6122c6149595f5f915c99ca4c7bd82e6415f1482
object d2e7c78c94e629a60bcff7b5c1abaf43e8ac7d75
type commit
tag v5.21.0-rc2
tagger l10n daemon script <scripty at kde.org> 1459716237 +0000

Create tag for 5.21.0


So, v5.21.0 is a tag on the 6122c6149595 object, which is a tag on the 
d2e7c78c94e6 commit.

Why doesn't v5.21.0 tag the d2e7c78c94e6 commit directly instead?

Thanks,

Steve.