The configuration file is used by `bitcoind`, `bitcoin-qt` and `bitcoin-cli`.
The configuration file is used by `litecoind`, `litecoin-qt` and `litecoin-cli`.
All command-line options (except for `-?`, `-help`, `-version` and `-conf`) may be specified in a configuration file, and all configuration file options (except for `includeconf`) may also be specified on the command line. Command-line options override values set in the configuration file and configuration file options override values set in the GUI.
@ -32,6 +32,6 @@ Network specific options can be:
## Configuration File Path
The configuration file is not automatically created; you can create it using your favorite text editor. By default, the configuration file name is `bitcoin.conf` and it is located in the Bitcoin data directory, but both the Bitcoin data directory and the configuration file path may be changed using the `-datadir` and `-conf` command-line options.
The configuration file is not automatically created; you can create it using your favorite text editor. By default, the configuration file name is `litecoin.conf` and it is located in the Litecoin data directory, but both the Litecoin data directory and the configuration file path may be changed using the `-datadir` and `-conf` command-line options.
The `includeconf=<file>` option in the `bitcoin.conf` file can be used to include additional configuration files.
The `includeconf=<file>` option in the `litecoin.conf` file can be used to include additional configuration files.
This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all` or `git fetch upstream-pull`. Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`, `git checkout` and anywhere a commit id would be acceptable to see the changes from pull request NUMBER.