add changelog entry for anthon's hynek-fication of options,

and change the docs and tests to use the new style.

doc/en/example/nonpython.txt

@@ -72,7 +72,7 @@ consulted when reporting in ``verbose`` mode::
 While developing your custom test collection and execution it's also
 interesting to just look at the collection tree::
 
-    nonpython $ py.test --collectonly
+    nonpython $ py.test --collect-only
     =========================== test session starts ============================
     platform linux2 -- Python 2.7.3 -- pytest-2.3.5
     collected 2 items

doc/en/example/parametrize.txt

@@ -114,7 +114,7 @@ this is a fully self-contained example which you can run with::
 If you just collect tests you'll also nicely see 'advanced' and 'basic' as variants for the test function::
 
 
-    $ py.test --collectonly test_scenarios.py
+    $ py.test --collect-only test_scenarios.py
     =========================== test session starts ============================
     platform linux2 -- Python 2.7.3 -- pytest-2.3.5
     collected 4 items
@@ -178,7 +178,7 @@ creates a database object for the actual test invocations::
 
 Let's first see how it looks like at collection time::
 
-    $ py.test test_backends.py --collectonly
+    $ py.test test_backends.py --collect-only
     =========================== test session starts ============================
     platform linux2 -- Python 2.7.3 -- pytest-2.3.5
     collected 2 items

doc/en/example/pythoncollection.py

@@ -1,5 +1,5 @@
 
-# run this with $ py.test --collectonly test_collectonly.py
+# run this with $ py.test --collect-only test_collectonly.py
 #
 def test_function():
     pass

doc/en/example/pythoncollection.txt

@@ -41,7 +41,7 @@ in functions and classes.  For example, if we have::
 
 then the test collection looks like this::
 
-    $ py.test --collectonly
+    $ py.test --collect-only
     =========================== test session starts ============================
     platform linux2 -- Python 2.7.3 -- pytest-2.3.5
     collected 2 items
@@ -80,7 +80,7 @@ Finding out what is collected
 
 You can always peek at the collection tree without running tests like this::
 
-    . $ py.test --collectonly pythoncollection.py
+    . $ py.test --collect-only pythoncollection.py
     =========================== test session starts ============================
     platform linux2 -- Python 2.7.3 -- pytest-2.3.5
     collected 3 items
@@ -133,7 +133,7 @@ and a setup.py dummy file like this::
 then a pytest run on python2 will find the one test when run with a python2 
 interpreters and will leave out the setup.py file::
     
-    $ py.test --collectonly
+    $ py.test --collect-only
     =========================== test session starts ============================
     platform linux2 -- Python 2.7.3 -- pytest-2.3.5
     collected 1 items