Skip to content

Rich/@comp.id decoding could also use the information from richprint #137

Description

@exoosh

comp_id.txt from richprint contains an up-to-date list of the IDs with product strings. And Go would even let you embed and parse that on the fly, if needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions