Originally created by @binki on GitHub (Oct 22, 2013).
If I want to refer directly to point number 10 in the 2.0.0 specification, I must use human language. If I could directly reference, via a relatively stable fragment identifier like #semver-buildmetadata, that particular point, that would reduce the amount of human work and potential for human error in referencing the spec.
Originally created by @binki on GitHub (Oct 22, 2013).
If I want to refer directly to point number 10 in the [2.0.0 specification](http://semver.org/spec/v2.0.0.html), I must use human language. If I could directly reference, via a relatively stable fragment identifier like `#semver-buildmetadata`, that particular point, that would reduce the amount of human work and potential for human error in referencing the spec.
@rfdrake commented on GitHub (Mar 31, 2016):
This was brought up again in issue #222 and https://github.com/mojombo/semver.org/issues/27 merged with https://github.com/mojombo/semver.org/commit/2af9fc3d40ac71cbb2c747d47241ccf46c8db9be
@binki, Id's have been added, along with link symbols when you mouse over the section numbers. Please close this issue at your earliest possible convenience. Thank you.
@jwdonahue commented on GitHub (Jul 15, 2018):
@binki, Id's have been added, along with link symbols when you mouse over the section numbers. Please close this issue at your earliest possible convenience. Thank you.
@binki, can you please close this issue? It has been resolved with a merge. All of the numbered spec and FAQ questions have been given Id's.
@jwdonahue commented on GitHub (Oct 8, 2018):
@binki, can you please close this issue? It has been resolved with a merge. All of the numbered spec and FAQ questions have been given Id's.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @binki on GitHub (Oct 22, 2013).
If I want to refer directly to point number 10 in the 2.0.0 specification, I must use human language. If I could directly reference, via a relatively stable fragment identifier like
#semver-buildmetadata, that particular point, that would reduce the amount of human work and potential for human error in referencing the spec.@eed3si9n commented on GitHub (Apr 7, 2015):
+1
@crazedsanity commented on GitHub (Apr 7, 2015):
+1
@rfdrake commented on GitHub (Mar 31, 2016):
This was brought up again in issue #222 and https://github.com/mojombo/semver.org/issues/27 merged with https://github.com/mojombo/semver.org/commit/2af9fc3d40ac71cbb2c747d47241ccf46c8db9be
@jwdonahue commented on GitHub (Jul 15, 2018):
@binki, Id's have been added, along with link symbols when you mouse over the section numbers. Please close this issue at your earliest possible convenience. Thank you.
@jwdonahue commented on GitHub (Oct 8, 2018):
@binki, can you please close this issue? It has been resolved with a merge. All of the numbered spec and FAQ questions have been given Id's.
@binki commented on GitHub (Oct 8, 2018):
@jwdonahue Looks good. Sorry for forgetting about this.