config: Bump POSIX spec references to IEEE Std 1003.1-2008, 2016 Edition#858
Merged
crosbymichael merged 1 commit intoopencontainers:masterfrom Jun 1, 2017
Merged
Conversation
wking
force-pushed
the
tk/bump-posix-spec
branch
2 times, most recently
from
c8ef4be to
3fb7d4b
Compare
These references had been using IEEE Std 1003.1, 2004 Edition, but: $ curl -s http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap08.html | grep -B2 'newer edition' <center><font size="2">The Open Group Base Specifications Issue 6<br> IEEE Std 1003.1, 2004 Edition<br> Copyright © 2001-2004 The IEEE and The Open Group, All Rights reserved.</font></center><center><font color="red">A newer edition of this document exists <a href="http://pubs.opengroup.org/onlinepubs/9699919799/" target="_parent">here</a></font></center> Shifting to 2016 also syncs us with the 'file' reference in config-linux.md. The initial reasoning for the 2004 edition is unclear to me (more on that in 70858bc, config: Adjust process.args to cite POSIX's execvp, 2016-05-19, opencontainers#427), The change-log for the exec page [1] doesn't list any relevant changes, and skimming a diff of the two HTML pages didn't turn up anything significant. Diffing the two HTML pages for environment variables also turned up no significant changes. Both definition reference the Portable Character Set for uppercase letters, digits, and underscore, but the U#### values for those have not changed [2,3]. [1]: http://pubs.opengroup.org/onlinepubs/9699919799/functions/exec.html#tag_16_111_14 [2]: http://pubs.opengroup.org/onlinepubs/009695399/basedefs/xbd_chap06.html#tag_06_01 [3]: http://pubs.opengroup.org/onlinepubs/9699919799/basedefs/V1_chap06.html#tag_06_01 Signed-off-by: W. Trevor King <wking@tremily.us>
Contributor
Author
Contributor
|
LGTM |
1 similar comment
Member
|
LGTM |
Merged
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
These references had been using IEEE Std 1003.1, 2004 Edition, but:
Shifting to 2016 also syncs us with the
filereference. The initial reasoning for the 2004 edition is unclear to me (more on that in 70858bc).The change-log for the
execpage doesn't list any relevant changes, and skimming a diff of the two HTML pages didn't turn up anything significant.Diffing the two HTML pages for environment variables also turned up no significant changes. Both definition reference the Portable Character Set for uppercase letters, digits, and underscore, but the
U####values for those have not changed.