Skip to content

Commit 3e55c8d

Browse files
author
Erlend Egeberg Aasland
authored
Remove outdated Mercurial references (python#799)
1 parent 255c7cc commit 3e55c8d

3 files changed

Lines changed: 12 additions & 13 deletions

File tree

gitbootcamp.rst

Lines changed: 9 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -344,30 +344,30 @@ When it happens, you need to resolve conflict. See these articles about resolvi
344344
- `About merge conflicts <https://help.github.com/en/articles/about-merge-conflicts>`_
345345
- `Resolving a merge conflict using the command line <https://help.github.com/en/articles/resolving-a-merge-conflict-using-the-command-line>`_
346346

347-
.. _git_from_mercurial:
347+
.. _git_from_patch:
348348

349-
Applying a Patch from Mercurial to Git
350-
--------------------------------------
349+
Applying a Patch to Git
350+
-----------------------
351351

352352
Scenario:
353353

354-
- A Mercurial patch exists but there is no pull request for it.
354+
- A patch exists but there is no pull request for it.
355355

356356
Solution:
357357

358358
1. Download the patch locally.
359359

360360
2. Apply the patch::
361361

362-
git apply /path/to/issueNNNN-git.patch
362+
git apply /path/to/patch.diff
363363

364364
If there are errors, update to a revision from when the patch was
365365
created and then try the ``git apply`` again:
366366

367367
.. code-block:: bash
368368

369369
git checkout $(git rev-list -n 1 --before="yyyy-mm-dd hh:mm:ss" main)
370-
git apply /path/to/issueNNNN-git.patch
370+
git apply /path/to/patch.diff
371371

372372
If the patch still won't apply, then a patch tool will not be able to
373373
apply the patch and it will need to be re-implemented manually.
@@ -382,6 +382,9 @@ Solution:
382382
git rebase main
383383
git mergetool
384384

385+
For very old changes, ``git merge --no-ff`` may be easier than a rebase,
386+
with regards to resolving conflicts.
387+
385388
6. Push the changes and open a pull request.
386389

387390
.. _git_pr:

pullrequest.rst

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -394,7 +394,7 @@ Author Name <email_address> ." to the pull request description and commit messag
394394
See `the GitHub article <https://help.github.com/articles/creating-a-commit-with-multiple-authors/>`_
395395
on how to properly add the co-author info.
396396

397-
See also :ref:`Applying a Patch from Mercurial to Git <git_from_mercurial>`.
397+
See also :ref:`Applying a Patch to Git <git_from_patch>`.
398398

399399
Reviewing
400400
---------

triaging.rst

Lines changed: 2 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -505,13 +505,9 @@ with the "open" status.
505505

506506
Mercurial Repository
507507
''''''''''''''''''''
508-
HTTP link to a Mercurial repository that contains a patch for the issue.
509-
A :guilabel:`Create Patch` button will appear that computes a diff for the
510-
head revision of the remote branch and attaches it to the issue. The button
511-
supports only CPython_ patches.
508+
Deprecated: HTTP link to a Mercurial repository that contains a patch for the issue.
512509

513-
If you don't indicate a remote branch, ``default`` is used. You can
514-
indicate a remote branch by adding ``#BRANCH`` to the end of the URL.
510+
New repository links should not be added to new or existing issues.
515511

516512
GitHub PR
517513
'''''''''

0 commit comments

Comments
 (0)