From fad389862725abe4351879e3333e47e9e5bf9e0c Mon Sep 17 00:00:00 2001 From: MarcoFalke Date: Mon, 13 Aug 2018 07:42:43 -0400 Subject: doc: move-only release notes of individual prs --- doc/release-notes-pr10267.md | 13 ----- doc/release-notes-pr10740.md | 10 ---- doc/release-notes-pr12257.md | 9 ---- doc/release-notes-pr12823.md | 20 -------- doc/release-notes-pr12892.md | 37 --------------- doc/release-notes-pr12924.md | 12 ----- doc/release-notes-pr13033.md | 11 ----- doc/release-notes.md | 111 +++++++++++++++++++++++++++++++++++++++++++ 8 files changed, 111 insertions(+), 112 deletions(-) delete mode 100644 doc/release-notes-pr10267.md delete mode 100644 doc/release-notes-pr10740.md delete mode 100644 doc/release-notes-pr12257.md delete mode 100644 doc/release-notes-pr12823.md delete mode 100644 doc/release-notes-pr12892.md delete mode 100644 doc/release-notes-pr12924.md delete mode 100644 doc/release-notes-pr13033.md (limited to 'doc') diff --git a/doc/release-notes-pr10267.md b/doc/release-notes-pr10267.md deleted file mode 100644 index 7e1967daf0..0000000000 --- a/doc/release-notes-pr10267.md +++ /dev/null @@ -1,13 +0,0 @@ -Changed command-line options ----------------------------- - -- `-includeconf=` can be used to include additional configuration files. - Only works inside the `bitcoin.conf` file, not inside included files or from - command-line. Multiple files may be included. Can be disabled from command- - line via `-noincludeconf`. Note that multi-argument commands like - `-includeconf` will override preceding `-noincludeconf`, i.e. - - noincludeconf=1 - includeconf=relative.conf - - as bitcoin.conf will still include `relative.conf`. diff --git a/doc/release-notes-pr10740.md b/doc/release-notes-pr10740.md deleted file mode 100644 index a2eb8cd837..0000000000 --- a/doc/release-notes-pr10740.md +++ /dev/null @@ -1,10 +0,0 @@ -Dynamic loading and creation of wallets ---------------------------------------- - -Previously, wallets could only be loaded or created at startup, by specifying `-wallet` parameters on the command line or in the bitcoin.conf file. It is now possible to load, create and unload wallets dynamically at runtime: - -- Existing wallets can be loaded by calling the `loadwallet` RPC. The wallet can be specified as file/directory basename (which must be located in the `walletdir` directory), or as an absolute path to a file/directory. -- New wallets can be created (and loaded) by calling the `createwallet` RPC. The provided name must not match a wallet file in the `walletdir` directory or the name of a wallet that is currently loaded. -- Loaded wallets can be unloaded by calling the `unloadwallet` RPC. - -This feature is currently only available through the RPC interface. diff --git a/doc/release-notes-pr12257.md b/doc/release-notes-pr12257.md deleted file mode 100644 index 293a00ad75..0000000000 --- a/doc/release-notes-pr12257.md +++ /dev/null @@ -1,9 +0,0 @@ -Notable changes -=============== - -Coin selection --------------- -- A new `-avoidpartialspends` flag has been added (default=false). If enabled, the wallet will try to spend UTXO's that point at the same destination - together. This is a privacy increase, as there will no longer be cases where a wallet will inadvertently spend only parts of the coins sent to - the same address (note that if someone were to send coins to that address after it was used, those coins will still be included in future - coin selections). diff --git a/doc/release-notes-pr12823.md b/doc/release-notes-pr12823.md deleted file mode 100644 index b493908716..0000000000 --- a/doc/release-notes-pr12823.md +++ /dev/null @@ -1,20 +0,0 @@ -Configuration sections for testnet and regtest ----------------------------------------------- - -It is now possible for a single configuration file to set different -options for different networks. This is done by using sections or by -prefixing the option with the network, such as: - - main.uacomment=bitcoin - test.uacomment=bitcoin-testnet - regtest.uacomment=regtest - [main] - mempoolsize=300 - [test] - mempoolsize=100 - [regtest] - mempoolsize=20 - -The `addnode=`, `connect=`, `port=`, `bind=`, `rpcport=`, `rpcbind=` -and `wallet=` options will only apply to mainnet when specified in the -configuration file, unless a network is specified. diff --git a/doc/release-notes-pr12892.md b/doc/release-notes-pr12892.md deleted file mode 100644 index f4a95bd40f..0000000000 --- a/doc/release-notes-pr12892.md +++ /dev/null @@ -1,37 +0,0 @@ -'label' and 'account' APIs for wallet -------------------------------------- - -A new 'label' API has been introduced for the wallet. This is intended as a -replacement for the deprecated 'account' API. The 'account' can continue to -be used in V0.17 by starting bitcoind with the '-deprecatedrpc=accounts' -argument, and will be fully removed in V0.18. - -The label RPC methods mirror the account functionality, with the following functional differences: - -- Labels can be set on any address, not just receiving addresses. This functionality was previously only available through the GUI. -- Labels can be deleted by reassigning all addresses using the `setlabel` RPC method. -- There isn't support for sending transactions _from_ a label, or for determining which label a transaction was sent from. -- Labels do not have a balance. - -Here are the changes to RPC methods: - -| Deprecated Method | New Method | Notes | -| :---------------------- | :-------------------- | :-----------| -| `getaccount` | `getaddressinfo` | `getaddressinfo` returns a json object with address information instead of just the name of the account as a string. | -| `getaccountaddress` | n/a | There is no replacement for `getaccountaddress` since labels do not have an associated receive address. | -| `getaddressesbyaccount` | `getaddressesbylabel` | `getaddressesbylabel` returns a json object with the addresses as keys, instead of a list of strings. | -| `getreceivedbyaccount` | `getreceivedbylabel` | _no change in behavior_ | -| `listaccounts` | `listlabels` | `listlabels` does not return a balance or accept `minconf` and `watchonly` arguments. | -| `listreceivedbyaccount` | `listreceivedbylabel` | Both methods return new `label` fields, along with `account` fields for backward compatibility. | -| `move` | n/a | _no replacement_ | -| `sendfrom` | n/a | _no replacement_ | -| `setaccount` | `setlabel` | Both methods now: