Commits

Jed Brown committed bf0c0a6

link formatting

Comments (0)

Files changed (1)

 # Following PETSc development
-The default branch in the PETSc repository is named [`master`](https://bitbucket.org/petsc/petsc/commits/all/tip/master).
+The default branch in the PETSc repository is named [master](https://bitbucket.org/petsc/petsc/commits/all/tip/master).
 It contains all features and bug fixes that are believed to be stable and will be in the next release.
 Users developing software based on recently-added features in PETSc should follow `master`:
 
     $ cd petsc
     $ git pull               # to get updates
 
-Features that are still experimental will be in the [`next`](https://bitbucket.org/petsc/petsc/commits/all/tip/next) branch.
+Features that are still experimental will be in the [next](https://bitbucket.org/petsc/petsc/commits/all/tip/next) branch.
 To use these features, and perhaps influence their design, follow `next` and discuss your concerns on the [petsc-dev mailing list](http://lists.mcs.anl.gov/pipermail/petsc-dev/) or by commenting on commits. After cloning, use
 
     $ git checkout next
     $ git pull               # to get updates
 
-You can `git checkout master` to get back to the more stable version.
+Use `git checkout master` to get back to the more stable version.
 
-Production users can follow the `maint` branch which contains the latest maintenance release plus any additional bug fixes.
-This should always be more stable than the latest tarball.
+Production users can follow the [maint](https://bitbucket.org/petsc/petsc/commits/all/tip/maint) branch, which contains the latest maintenance release plus any additional bug fixes.
+It should always be more stable than the latest tarball.
 
 # Contributing to PETSc
 
 
 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).
 
-[Read detailed instructions for Git](developer-instructions-git) - [Quick Summary](quick-dev-git)
+[Read detailed instructions for Git](developer-instructions-git) - [Quick Summary](quick-dev-git)