Skip to content

Commit

Permalink
added blank line to ensure markdown does create an unordered list (ma…
Browse files Browse the repository at this point in the history
…ndatory)
  • Loading branch information
robbiemorrison committed Nov 2, 2023
1 parent 5b7f552 commit 234d060
Showing 1 changed file with 1 addition and 0 deletions.
1 change: 1 addition & 0 deletions Chapters/5.Core_identifiers.md
Original file line number Diff line number Diff line change
Expand Up @@ -151,6 +151,7 @@ As an example, `swh:1:rev:309cf2674ee7a0749978cf8265ab91a60aea0f7d` is the SWHID
Some revisions get selected by developers as denoting important project milestones known as “releases”. Each release points to the last commit in project history corresponding to that release and carries metadata: release name and version, release message, cryptographic signatures, and so forth. If they're not attached to development history (for instance, if they've been imported from bare archive files), releases can also point directly to a root directory instead of a full revision with metadata.

The metadata fields supported by SWHID are as follows:

- name (arbitrary byte sequence, mandatory): a name identifying the release
- author (arbitrary byte sequence): generally contains the name and email address of the author of the release.
- author timestamp (decimal timestamp from the Unix epoch): the date at which the release was authored.
Expand Down

0 comments on commit 234d060

Please sign in to comment.