Re: git tag -v should verify that the tag signer intended the same tag name as the user is verifying
- From
- Daniel Kahn Gillmor <dkg@fifthhorseman.net>
- Date
- Mar 24, 2019, 15:07 UTC
- Message-ID
- <87k1goia52.fsf@fifthhorseman.net>
- In-Reply-To
- <xmqqpnqgpifu.fsf@gitster-ct.c.googlers.com>
On Sun 2019-03-24 21:26:13 +0900, Junio C Hamano wrote:
Show 18 quoted lines
> Daniel Kahn Gillmor <dkg@fifthhorseman.net> writes: > >> I don't personally have any use case for doing such a tag rename -- you >> mention two: >> >> a) wanting to call tag "foo" that you found on remote "origin" by the >> name of "origin/foo" >> >> b) wanting to call "v2.20.0" by the name "g2.20.0" > > For the record, in the latter there is no "wanting to call". It was > merely a set-up used to illustrate what support there already exists > in the current system that helps making users aware of tags that are > not stored in there "natural" place. > > The former however is a natural consequence of noises people make > around here from time to time, wanting to have tags you grab from > elsewhere and tags you create locally in separate places.
Gotcha, thanks. I like the warnings that are already showing up from (b) So I won't worry about (b) as a justification then, but rather keep my focus on (a). (and i still think that (c) has better solutions than tag renaming)
What do you think of my updated proposal for tag.verifyNameMatch ?
--dkg