Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.bugs.dist > #1234188

Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields

From Simon Josefsson <simon@josefsson.org>
Newsgroups linux.debian.bugs.dist, linux.debian.policy
Subject Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields
Date 2025-02-20 11:30 +0100
Message-ID <KibYC-AtA-25@gated-at.bofh.it> (permalink)
References (2 earlier) <Kibcd-zW2-5@gated-at.bofh.it> <K0czM-4OVR-13@gated-at.bofh.it> <KibYC-AtA-27@gated-at.bofh.it> <K0czM-4OVR-13@gated-at.bofh.it> <KibYC-AtA-27@gated-at.bofh.it>
Organization linux.* mail to news gateway

Cross-posted to 2 groups.

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Sean Whitton <spwhitton@spwhitton.name> writes:

> +The value is of the form ``tag=TAGOBJID fp=FINGERPRINT`` where ``TAGOBJID`` is
> +the Git object ID of the Git tag object, and ``FINGERPRINT`` is the
> +fingerprint (in hexadecimal, without spaces) of the PGP key used to sign the
> +Git tag.

What restrictions on the formats of TAGOBJID and/or FINGERPRINT are
implicit here?

Do consumers of this field have to handle both SHA1 and SHA256 git
object ids?

OpenPGP v5 or v6 fingerprint?

How are they supposed to behave if they cannot understand parts of the
information in the header?

/Simon

Back to linux.debian.bugs.dist | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread

Thread

Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-02-20 10:40 +0100
  Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-20 11:10 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-03-05 02:50 +0100
  Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Simon Josefsson <simon@josefsson.org> - 2025-02-20 11:30 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-20 11:40 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Guillem Jover <guillem@debian.org> - 2025-02-20 13:00 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-02-20 17:20 +0100
  Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sam Hartman <hartmans@debian.org> - 2025-02-20 17:50 +0100
    Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-21 04:10 +0100
      Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Ian Jackson <ijackson@chiark.greenend.org.uk> - 2025-02-21 17:30 +0100
        Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-22 02:30 +0100
      Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sam Hartman <hartmans@debian.org> - 2025-02-22 00:40 +0100
        Bug#1091868: debian-policy: Document Git-Tag-Tagger and Git-Tag-Info fields Sean Whitton <spwhitton@spwhitton.name> - 2025-02-22 02:10 +0100

csiph-web