diff options
| author | Tom Stellard <tstellar@redhat.com> | 2017-09-19 03:27:26 +0000 | 
|---|---|---|
| committer | Tom Stellard <tstellar@redhat.com> | 2017-09-19 03:27:26 +0000 | 
| commit | 8852087517ec8c72f4748438d920421c44fbd690 (patch) | |
| tree | e41572d100d9938e3575b47fba940b077b8c408e /llvm/docs | |
| parent | c902f6f4cc0e387591661f62fad22034a6ada0f1 (diff) | |
| download | bcm5719-llvm-8852087517ec8c72f4748438d920421c44fbd690.tar.gz bcm5719-llvm-8852087517ec8c72f4748438d920421c44fbd690.zip  | |
docs: Fix formatting in HowToReleaseLLVM
This is a follow up to r313608.
llvm-svn: 313609
Diffstat (limited to 'llvm/docs')
| -rw-r--r-- | llvm/docs/HowToReleaseLLVM.rst | 16 | 
1 files changed, 8 insertions, 8 deletions
diff --git a/llvm/docs/HowToReleaseLLVM.rst b/llvm/docs/HowToReleaseLLVM.rst index fdc48cb4ad4..ec3362e97b6 100644 --- a/llvm/docs/HowToReleaseLLVM.rst +++ b/llvm/docs/HowToReleaseLLVM.rst @@ -263,18 +263,18 @@ You can use any of the following methods to request that a revision from trunk  be merged into a release branch:  #. Use the ``utils/release/merge-request.sh`` script which will automatically -file a bug_ requesting that the patch be merged. e.g. To request revision -12345 be merged into the branch for the 5.0.1 release: -``llvm.src/utils/release/merge-request.sh -stable-version 5.0 -r 12345 -user bugzilla@example.com`` +   file a bug_ requesting that the patch be merged. e.g. To request revision +   12345 be merged into the branch for the 5.0.1 release: +   ``llvm.src/utils/release/merge-request.sh -stable-version 5.0 -r 12345 -user bugzilla@example.com``  #. Manually file a bug_ with the subject: "Merge r12345 into the X.Y branch", -enter the commit(s) that you want merged in the "Fixed by Commit(s)" and mark -it as a blocker of the current release bug.  Release bugs are given aliases -in the form of release-x.y.z, so to mark a bug as a blocker for the 5.0.1 -release, just enter release-5.0.1 in the "Blocks" field. +   enter the commit(s) that you want merged in the "Fixed by Commit(s)" and mark +   it as a blocker of the current release bug.  Release bugs are given aliases +   in the form of release-x.y.z, so to mark a bug as a blocker for the 5.0.1 +   release, just enter release-5.0.1 in the "Blocks" field.  #. Reply to the commit email on llvm-commits for the revision to merge and cc -the release manager. +   the release manager.  .. _bug: https://bugs.llvm.org/  | 

