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

Update trunk-repos.html.md #1112

Merged
merged 2 commits into from
Nov 27, 2017
Merged

Conversation

vikasmulaje
Copy link
Contributor

Change URL of trunk repo package

Change URL of trunk repo package
Change description to suit the URL
@vikasmulaje vikasmulaje mentioned this pull request Nov 26, 2017
@@ -26,7 +26,7 @@ For stable releases, we also follow the upper-constraints approach.

## Hashed repos and special repos

When each new upstream commit is built, a repository is created with the new package and the latest versions from every other package built by RDO Trunk. This new repository is located in a hashed URL, for example [https://trunk.rdoproject.org/centos7/51/29/51299ba1eca22462c5560854f53b668ad7872ac7_18d76a1f/](https://trunk.rdoproject.org/centos7/51/29/51299ba1eca22462c5560854f53b668ad7872ac7_18d76a1f/). This hash is built using:
When each new upstream commit is built, a repository is created with the new package and the latest versions from every other package built by RDO Trunk. This new repository is located in a hashed URL. The details can be found at [https://www.rdoproject.org/what/trunk-repos/](https://www.rdoproject.org/what/trunk-repos/). This hash is built using:
Copy link
Contributor

Choose a reason for hiding this comment

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

Altough the link is broken the point of this section is to explain the format of the url for hashed repos, and i think it's useful to keep it. We purge repos older that 60 days so it's difficult to keep updated info. Anyway, IMO the fact that the link is not as important as understanding what each part of the url means.

Copy link
Contributor

Choose a reason for hiding this comment

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

If the URL is an explanation, then we should not create a clickable link. We can use backslashes to create inline code, so we can show the URL without having the Markdown parser create a link for it.

@rbowen rbowen merged commit 29324a7 into redhat-openstack:master Nov 27, 2017
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 this pull request may close these issues.

4 participants