Commits

Jed Brown committed 790b372

unlink Hg instructions

Comments (0)

Files changed (1)

 
 # Contributing to PETSc
 
-The most efficient way to create any patch or new functionality is to use a version control system. We recommend Git, but can also deal with Mercurial.
+The most efficient way to create any patch or new functionality is to use the Git version control system.
 
 ## Contributing a Small Patch
 
 *Pull requests are preferred over patches. For only a small set of changes a patch is fine.*
 
-The recommended way of creating a patch is to clone the petsc-repository, create a new branch on your local repository from master, apply and commit your changes there, and let Git/Mercurial create the patch. Send the patch to [petsc-dev@mcs.anl.gov](mailto:petsc-dev@mcs.anl.gov).
+The recommended way of creating a patch is to clone the [petsc](https://bitbucket.org/petsc/petsc) repository, create a new branch on your local repository from master, apply and commit your changes there, and use `git format-patch origin/master` to create the patch. Send the patch to [petsc-dev@mcs.anl.gov](mailto:petsc-dev@mcs.anl.gov).
 
 [Read detailed instructions for git](patch-instructions-git)
 
-[Read detailed instructions for Mercurial](patch-instructions-mercurial)
-
 ## Contributing a Larger Piece of Functionality
 
-For changes spanning more than just a few lines, handling patches hampers a quick review and is thus not efficient. Instead, the recommended way is to provide pull-requests via a fork of the [PETSc repository](https://bitbucket.org/petsc/petsc) ([Hg mirror](https://bitbucket.org/petsc/petsc-hg)) here on Bitbucket by clicking on 'Fork' in the upper right. Clone the PETSc repository as usual, code your new feature in a separate branch of your clone (Git) or directly in master (Mercurial), and push the new branch to the forked repository to send a pull request by clicking on [Pull request](https://bitbucket.org/petsc/petsc/pull-request/new) on the upper right. 
+For changes spanning more than just a few lines, handling patches hampers a quick review and is thus not efficient. Instead, the recommended way is to provide pull-requests via a fork of the [PETSc repository](https://bitbucket.org/petsc/petsc) here on Bitbucket by clicking on 'Fork' in the upper right. Clone the PETSc repository as usual, code your new feature in a separate branch of your clone, and push the new branch to the forked repository to send a pull request by clicking on [Pull request](https://bitbucket.org/petsc/petsc/pull-request/new) on the upper right. 
 
 [Read detailed instructions for Git](pull-request-instructions-git)
 
-[Read detailed instructions for Mercurial](pull-request-instructions-mercurial)
-
-
 ## PETSc Development Workflow
 
 If you have direct write (push) access to the PETSc repository, you should be familiar with our development workflow. We use a simplified version of the `master`/`next` workflow used by the Linux kernel developers. This allows parallel development of multiple features at the same time while preserving a stable `master` branch. The model is explained in [gitworkflows(7)](https://www.kernel.org/pub/software/scm/git/docs/gitworkflows.html) (but we do not currently use a `pu` branch).