aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorWladimir J. van der Laan <laanwj@gmail.com>2015-07-27 14:54:53 +0200
committerWladimir J. van der Laan <laanwj@gmail.com>2015-07-27 14:55:15 +0200
commitc6455c77ab90910bf4c03005fb0a7dfe785e7087 (patch)
tree68c75f17e52d83ab9f60926c912d2820edfd02f0 /doc
parentc38c49d0b708cf948eb46e0857eb743cda09980c (diff)
downloadbitcoin-c6455c77ab90910bf4c03005fb0a7dfe785e7087.tar.xz
doc: mention change to option parsing behavior in release notes
Diffstat (limited to 'doc')
-rw-r--r--doc/release-notes.md8
1 files changed, 8 insertions, 0 deletions
diff --git a/doc/release-notes.md b/doc/release-notes.md
index 7480a7cd21..db6c28972d 100644
--- a/doc/release-notes.md
+++ b/doc/release-notes.md
@@ -27,6 +27,14 @@ Low-level RPC API changes
advantage if a JSON library insists on using a lossy floating point type for
numbers, which would be dangerous for monetary amounts.
+Option parsing behavior
+-----------------------
+
+Command line options are now parsed strictly in the order in which they are
+specified. It used to be the case that `-X -noX` ends up, unintuitively, with X
+set, as `-X` had precedence over `-noX`. This is no longer the case. Like for
+other software, the last specified value for an option will hold.
+
0.12.0 Change log
=================