fixed documentation on disabling/enabling hardening flags #3411

This is resolution to #3367, fixing incorrect github commit merge

Can you please give the commit a more descriptive name instead of "Changes" ?

BTW you don't have to open a new pull request if you make a change, you can just re-push to the same branch and the existing pull will be updated.

"BTW you don't have to open a new pull request if you make a change, you can just re-push to the same branch and the existing pull will be updated."

No. The repo was corrupted. The original pull request was not listed in the set of pull requests on github. I had to delete the repo and then recreate it and there was a 501 error. I had to contact technical support. The pull request was no longer associated with the repo.

There was no option for amending the pull request and the previous branch no longer existed.

On Fri, Dec 13, 2013 at 3:59 AM, BitcoinPullTester <notifications@github.com

wrote:

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/1d2feb2da68c7ccd69b4b3d74eaaa65b5715a3e8for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.

— Reply to this email directly or view it on GitHubhttps://github.com/bitcoin/bitcoin/pull/3411#issuecomment-30504509 .

I renamed the commit message.

Automatic sanity-testing: PASSED, see http://jenkins.bluematt.me/pull-tester/08b93f9a65ce70e650244f94725fcd042d97f0ee for binaries and test log. This test script verifies pulls every time they are updated. It, however, dies sometimes and fails to test properly. If you are waiting on a test, please check timestamps to verify that the test.log is moving at http://jenkins.bluematt.me/pull-tester/current/ Contact BlueMatt on freenode if something looks broken.