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

Fix hyperlink to public URI for a GitHub issue #680

Merged
merged 2 commits into from
Nov 30, 2018

Conversation

sftim
Copy link
Contributor

@sftim sftim commented Nov 28, 2018

The FAQ has a link a GitHub issue in what looks like a previous, private incarnation of this repo. Link to the current URI of that issue instead.

Copy link
Contributor

@acatangiu acatangiu left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Although all PRIVATE-firecracker links successfully redirect to the new repo location, this is a valid change that avoids confusion.

A grep through the repo for PRIVATE also shows

mmds/src/data_store.rs:40:        // https://github.com/aws/PRIVATE-firecracker/issues/401

so it'd be great if you could also change that in this PR.

Seems like the Firecracker repo is now public at
https://github.com/firecracker-microvm

Signed-off-by: Tim Bannister <tim+github@scalefactory.com>
Copy link
Contributor

@raduweiss raduweiss left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me.

@raduweiss raduweiss added Documentation: Usage Type: Bug Indicates an unexpected problem or unintended behavior labels Nov 28, 2018
@aghecenco aghecenco merged commit b0163cb into firecracker-microvm:master Nov 30, 2018
@sftim sftim deleted the 20181128_repo_uri_fix branch December 4, 2018 12:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Type: Bug Indicates an unexpected problem or unintended behavior
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants