Skip to content

Custom section name recommendations to avoid conflicts #243

@lann

Description

@lann

Custom sections are identified by unstructured string names, which presents the possibility of conflicts between different tools. This repo helps the situation by acting as a pseudo-registry of some "publicly well-known" custom section names, but doesn't help with less-common or private tooling.

I'd like to suggest that this repo publish a recommendation for formatting custom section names to help avoid conflicts. One obvious source of inspiration might be vendor mime types (e.g. vnd.acme.whatever) but I'm less concerned about the exact format than the general idea.

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