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.

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

The reference to "schema/schema.json" is bad #517

Closed
hapnermw opened this issue Jul 18, 2016 · 2 comments · Fixed by #519
Closed

The reference to "schema/schema.json" is bad #517

hapnermw opened this issue Jul 18, 2016 · 2 comments · Fixed by #519

Comments

@hapnermw
Copy link

No description provided.

@wking
Copy link
Contributor

wking commented Jul 18, 2016

This is probably talking about 1, which should have been updated in
#481 or the #498 fixup. Are you working on a PR, or shall I submit
one?

@vbatts
Copy link
Member

vbatts commented Jul 18, 2016

hmm. @hapnermw do you have any more specifics?

wking added a commit to wking/opencontainer-runtime-spec that referenced this issue Jul 19, 2016
This slipped through the rename in 2a5986f (schema/state-schema.json:
Add a JSON Schema for the state JSON, 2016-06-01, opencontainers#481) and the first
round of fixes in dfb85b1 (schema/README: Fix links to
(config|state)-schema.json, 2016-06-13, opencontainers#498).  Reported by hapnermw
[1].

[1]: opencontainers#517

Signed-off-by: W. Trevor King <[email protected]>
Mashimiao pushed a commit to Mashimiao/specs that referenced this issue Aug 19, 2016
This slipped through the rename in 2a5986f (schema/state-schema.json:
Add a JSON Schema for the state JSON, 2016-06-01, opencontainers#481) and the first
round of fixes in dfb85b1 (schema/README: Fix links to
(config|state)-schema.json, 2016-06-13, opencontainers#498).  Reported by hapnermw
[1].

[1]: opencontainers#517

Signed-off-by: W. Trevor King <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants