Memory Config: get Event ID reply

[balazsracz]

In #102 we noted that the number of event IDs requested in three bits is 0-7. We forgot to update the text in the Get Event ID reply. That oner still says 1-8 events are returned when correctly it is 0-7.

[bobjacobsen]

Can we fix this with a PR to standards/MemoryConfigurationS.* and the .txt file? or do we need to go through /drafts/ to get the proper history? Happy to do that 2nd thing if it's really needed.

[balazsracz]

We can edit in place in the standards directory, but this will not update the changes/xxx-date.pdf file. It is not super useful to create a new file with a different date and only one line of change.

I see a few options: 1) punt. Take care of this whenever we update the standards next time. This is why I filed the issue, so that we don't forget. 2) Update the changes in a bit of a roundabout way:

• go back in the git history when you had the ODT from which the -changes-date.pdf was created.
• apply the update there
• regenerate the -changes-date.pdf
• save it outside of the git directory
• check out master, create a new branch
• edit the ODT in the standards directory
• apply the same change (you have to do this by hand I think).
• regenerate pdf and txt
• copy back the -changes.pdf to overwrite the previous one
• commit all of this and merge to master 3) There is a third option where we roll back head to the commit before "accepting all changes", update the single file there, and redo the adoption process from there on.

[bobjacobsen]

PR #135 is your method (2) above. But note that the diffs in that PR are not what I would have expected. They look like they create the right final state, but they seem to not take into effect the previous adopted docs.