Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly
Appearance settings

Commit 135576e

Browse filesBrowse files
NelleVQuLogic
NelleV
authored and
QuLogic
committed
Merge pull request #7286 from afvincent/doc_fix_url_development_workflow
DOC: Fix for #7283 by adding a trailing underscore to misrendered URLs
1 parent 9c1b548 commit 135576e
Copy full SHA for 135576e

File tree

Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed
Filter options
Expand file treeCollapse file tree

1 file changed

+2
-2
lines changed

‎doc/devel/gitwash/development_workflow.rst

Copy file name to clipboardExpand all lines: doc/devel/gitwash/development_workflow.rst
+2-2Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -160,9 +160,9 @@ upstream changes, and resolving conflicts.
160160
In git, rebasing is a mild form of re-writing history: it effectively forwards
161161
all your commits to the updated upstream commit. For a much more detailed
162162
explanation (with pictures!) see `this nice write up
163-
<https://git-scm.com/book/en/Git-Branching-Rebasing>`. The NumPy team has also
163+
<https://git-scm.com/book/en/Git-Branching-Rebasing>`_. The NumPy team has also
164164
`documented how to do this
165-
<http://docs.scipy.org/doc/numpy/dev/gitwash/development_workflow.html#rebasing-on-master>`
165+
<http://docs.scipy.org/doc/numpy/dev/gitwash/development_workflow.html#rebasing-on-master>`_.
166166
In general, re-writing history, particularly published history, is considered
167167
bad practice, but in this case it is very useful.
168168

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.