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 README #1678

Merged
merged 1 commit into from
Jun 7, 2021
Merged

update README #1678

merged 1 commit into from
Jun 7, 2021

Conversation

acomodi
Copy link
Contributor

@acomodi acomodi commented May 25, 2021

Signed-off-by: Alessandro Comodi acomodi@antmicro.com

fixes #1674

Signed-off-by: Alessandro Comodi <acomodi@antmicro.com>

### Step 9: ###
Pick a fuzzer (or write your own) and run:
Pick a fuzzer (or write your own), from the ``prjxray`` root dir, run:
Copy link
Contributor

Choose a reason for hiding this comment

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

Why the double backticks around prjxray?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

No reason apart from keeping consistency with the step 2

Copy link
Contributor

Choose a reason for hiding this comment

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

Shouldn't single backticks be enough?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Hmm yeah, I think should be enough actually, not sure why we started to use double backticks. If we can postpone merging this and wait for another CI run, I can change this

Copy link
Contributor

@mithro mithro left a comment

Choose a reason for hiding this comment

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

LGTM!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Documentation Issue
2 participants