On Mon 2019-03-25 11:27:06 +0900, Junio C Hamano wrote: > Daniel Kahn Gillmor <[email protected]> writes: > >> What do you think of my updated proposal for tag.verifyNameMatch ? > > Meh to slightly negative for hard-coding project-specific preference > to the core tools. "We give you --format so go wild in your project > to do verification your project likes." I think was the conclusion of > the previous round of discussions, and I do not think we saw any new > arguments in this round to rethink it in a different way.
Hm, maybe --format is all that's necessary to resolve the concerns about
errors affecting scenario (a) ? If that's the case, then maybe the path
forward is a warning on tagname mismatch (and maybe i can convince you
later than an actual error could be acceptable :P)
But I don't see how to use --format with "git tag -v" at all. Can you
show me what i'm doing wrong? git-tag(1) says that --format defaults to
'%(refname:strip=2)', but git tag -v behaves differently when i specify
that same default explicitly:
0 dkg@alice:~/src/pkg-gnupg/gnupg2$ git tag -v gnupg-2.2.13
object 7922e2dd1c7eee48a8a2cf4799827942489ddd0f
type commit
tag gnupg-2.2.13
tagger Werner Koch <[email protected]> 1549985965 +0100
You may want to watch the Ellsberg/Chomsky discussion
at
<https://riseuptimes.org/2018/04/25/daniel-ellsberg-and-noam-chomsky-discuss-nuclear-war/>
or at <https://theintercept.com/chomsky-ellsberg/>
gpg: Signature made Tue 12 Feb 2019 04:41:32 PM CET
gpg: using RSA key D8692123C4065DEA5E0F3AB5249B39D24F25E3B6
gpg: Good signature from "Werner Koch (dist sig)" [full]
Primary key fingerprint: D869 2123 C406 5DEA 5E0F 3AB5 249B 39D2 4F25 E3B6
0 dkg@alice:~/src/pkg-gnupg/gnupg2$ git tag -v
--format='%(refname:strip=2)' gnupg-2.2.13
0 dkg@alice:~/src/pkg-gnupg/gnupg2$
What am i missing?
--dkg
signature.asc
Description: PGP signature
