Skip to content

Fix incorrect backtick usage in inline code #436

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

Merged
merged 1 commit into from
Sep 10, 2020

Conversation

benediktwerner
Copy link
Contributor

@benediktwerner benediktwerner commented Sep 10, 2020

Just a small formatting/markdown fix. Rendered diff says it all.

@XAMPPRocky
Copy link
Member

Thank you for your PR, and congrats on your first contribution! 🎉 I didn't know about double backticks, good to remember.

@XAMPPRocky XAMPPRocky merged commit 2866582 into rust-lang:master Sep 10, 2020
@@ -63,7 +63,7 @@ We need to find out the parent commit in which the PR opened last Monday merged.

Go to that PR, and find the "bors merged commit $SHA into rust-lang:master at the bottom.

Locally, run `export BRANCH_POINT=`git rev-parse $SHA^` in the rust-lang/rust
Locally, run `` export BRANCH_POINT=`git rev-parse $SHA^` `` in the rust-lang/rust
Copy link
Contributor

Choose a reason for hiding this comment

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

Why not use $(command) instead ? This form is recommended by bash.

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.

3 participants