Skip to content

Fix repository_tool documentation header #177

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

Closed
trishankkarthik opened this issue Feb 24, 2014 · 2 comments
Closed

Fix repository_tool documentation header #177

trishankkarthik opened this issue Feb 24, 2014 · 2 comments
Labels
documentation Documentation of the project as well as procedural documentation

Comments

@trishankkarthik
Copy link
Contributor

The header "Create TUF Repository" is a bit misleading, because the code example is not creating a new repository, but rather loading an old one.

We should either change the heading to reflect the example, or change the example to reflect the header.

@trishankkarthik trishankkarthik added this to the TUF 1.0 milestone Feb 24, 2014
@vladimir-v-diaz
Copy link
Contributor

You should report issues in the pull request.
#170

That header contains many sub-sections, not just that introductory example. The header formatting might not be clear.

Create TUF Repository
    Keys
    Create a new Repository
    Delegations
    etc.
Client Setup

@vladimir-v-diaz
Copy link
Contributor

Table of Contents added: 511382b

ivanayov pushed a commit to ivanayov/python-tuf that referenced this issue Nov 18, 2021
This change edits the ngclient `Updater` to traverse the delegation
tree on nodes, instead of edges in order to skip already visited
nodes. For more detailed clarification, please review theupdateframework#177

Fixes theupdateframework#1528

Signed-off-by: Ivana Atanasova <iyovcheva@iyovcheva-a02.vmware.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Documentation of the project as well as procedural documentation
Projects
None yet
Development

No branches or pull requests

2 participants