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.
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
Issue 175 make query chap #391
Conversation
Can squash this later which will get rid of this move, but I do it this way so that you can see how we changed the text in this new chapter instead of it all appearing as if it is new text. Signed-off-by: dsolt@us.ibm.com
This PR uses 2 commits in a slightly strange way that allows you to look at just the changes for the 2nd commit and see how the material in the new chapter changed from what it was before. That is hard to see if you just look at the combined changes. |
Especially separating out attributes from keys, moving query structure to the start of the chapter and adding chapter headings, etc. Signed-off-by: dsolt@us.ibm.com
e3017b4
to
bcd8884
Compare
Please use emoji reactions ON THIS COMMENT to indicate your position on this proposal.
Here are the meanings for the emojis:
|
Here is a pdf showing the changes to this chapter with green highlighting for new text, red for changed text and grey for moved text. |
Signed-off-by: dsolt@us.ibm.com
singular use of query vs queries in intro permissable -> permissible any keys -> any particular keys when describing what implementations must support block of text that was accidentally not moved with the list of attributes that where moved. similified -> simplified Signed-off-by: dsolt@us.ibm.com
PMIx ASC 1Q 2022
|
PMIx ASC 2Q 2022
|
Rebased version in #407 |
Closing in favor of PR #407 - which is the same content, but rebased onto the current |
This PR moves functions related to querying the system in general to their own chapter. This leaves the chapter they were taken from very small, especially when accounting for #390 which also removes material from the same chapter. However,
yet another PR is forthcoming which will address what remains of the Chap_API_Sync_Access chapter.