Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

content/static/doc: make clear when pseudo versions will be used #34

Open
wants to merge 1 commit into
base: master
Choose a base branch
from
+3 −3
Open

content/static/doc: make clear when pseudo versions will be used #34

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions content/static/doc/mod.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -139,9 +139,9 @@ A <dfn>pseudo-version</dfn> is a specially formatted
information about a specific revision in a version control repository. For
example, `v0.0.0-20191109021931-daa7c04131f5` is a pseudo-version.

Pseudo-versions may refer to revisions for which no [semantic version
tags](#glos-semantic-version-tag) are available. They may be used to test
commits before creating version tags, for example, on a development branch.
Pseudo-versions may refer to revisions for which no canonical version tags are
available. They may be used to test commits before creating version tags, for
example, on a development branch.

Each pseudo-version has three parts:

Expand Down