maxmustermann/dogecoin
1
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity
11551 commits 12 branches 161 tags 1.2 GiB
C++ 65.7%
Python 15%
C 12.5%
M4 2.7%
Makefile 1.5%
Other 2.5%
Go to file
Wladimir J. van der Laan 7e9ab9555c
Merge #8608: Install manpages via make install, also add some autogenerated manpages 
d19583f improved gen-manpages.sh, includes bitcoin-tx and strips commit tag, now also runs binaries from build dir by default, added variables for more control (nomnombtc)
09546ca regenerated all manpages with commit tag stripped, also add bitcoin-tx (nomnombtc)
ae6e754 change help string --enable-man to --disable-man (nomnombtc)
a32c102 add conditional for --enable-man, default is yes (nomnombtc)
dc84b6f add doc/man to subdir if configure flag --enable-man is set (nomnombtc)
00dba72 add doc/man/Makefile.am to include manpages (nomnombtc)
eb5643b add autogenerated manpages by help2man (nomnombtc)
6edf2fd add gen-manpages.sh description to README.md (nomnombtc)
d2cd9c0 add script to generate manpages with help2man (nomnombtc)
2016-09-13 10:34:55 +02:00
.github Adds issue template. [skip ci] 2016-08-10 12:25:52 -05:00
.tx tx: change slug to bitcoin.qt-translation-013x 2016-06-28 11:49:30 +02:00
build-aux/m4 Add configure check for -latomic 2016-08-23 16:55:15 +10:00
contrib Merge #8608: Install manpages via make install, also add some autogenerated manpages 2016-09-13 10:34:55 +02:00
depends Remove unused Qt 4.6 patch. 2016-09-01 17:20:44 -07:00
doc Merge #8608: Install manpages via make install, also add some autogenerated manpages 2016-09-13 10:34:55 +02:00
qa Merge #8667: Fix SIGHASH_SINGLE bug in test_framework SignatureHash 2016-09-09 23:20:21 +02:00
share Merge #8270: Tests: Use portable #! in python scripts (/usr/bin/env) 2016-08-15 15:45:20 +02:00
src Merge #8678: [Qt][CoinControl] fix UI bug that could result in paying unexpected fee 2016-09-09 14:34:03 +02:00
.gitattributes Separate protocol versioning from clientversion 2014-10-29 00:24:40 -04:00
.gitignore [qa] Use single cache dir for chains 2016-08-07 23:13:22 +02:00
.travis.yml [travis] Drop java 2016-08-17 21:35:48 +02:00
autogen.sh autogen.sh: warn about needing autoconf if autoreconf is not found 2016-02-13 04:44:42 +08:00
configure.ac Merge #8608: Install manpages via make install, also add some autogenerated manpages 2016-09-13 10:34:55 +02:00
CONTRIBUTING.md contributing.md: Fix formatting 2016-06-23 08:40:06 -06:00
COPYING Update license year range to 2016 2016-01-17 23:38:11 +05:30
INSTALL
libbitcoinconsensus.pc.in Unify package name to as few places as possible without major changes 2015-12-14 02:11:10 +00:00
Makefile.am add doc/man to subdir if configure flag --enable-man is set 2016-08-27 01:09:22 +02:00
README.md readme: Omit phrasing; 'new' 2016-06-19 14:15:58 -06:00

README.md

Bitcoin Core integration/staging tree

Build Status

https://bitcoincore.org

What is Bitcoin?

Bitcoin is an experimental digital currency that enables instant payments to anyone, anywhere in the world. Bitcoin uses peer-to-peer technology to operate with no central authority: managing transactions and issuing money are carried out collectively by the network. Bitcoin Core is the name of open source software which enables the use of this currency.

For more information, as well as an immediately useable, binary version of the Bitcoin Core software, see https://bitcoin.org/en/download, or read the original whitepaper.

License

Bitcoin Core is released under the terms of the MIT license. See COPYING for more information or see https://opensource.org/licenses/MIT.

Development Process

The master branch is regularly built and tested, but is not guaranteed to be completely stable. Tags are created regularly to indicate new official, stable release versions of Bitcoin Core.

The contribution workflow is described in CONTRIBUTING.md.

The developer mailing list should be used to discuss complicated or controversial changes before working on a patch set.

Developer IRC can be found on Freenode at #bitcoin-core-dev.

Testing

Testing and code review is the bottleneck for development; we get more pull requests than we can review and test on short notice. Please be patient and help out by testing other people's pull requests, and remember this is a security-critical project where any mistake might cost people lots of money.

Automated Testing

Developers are strongly encouraged to write unit tests for new code, and to submit new unit tests for old code. Unit tests can be compiled and run (assuming they weren't disabled in configure) with: make check

There are also regression and integration tests of the RPC interface, written in Python, that are run automatically on the build server. These tests can be run (if the test dependencies are installed) with: qa/pull-tester/rpc-tests.py

The Travis CI system makes sure that every pull request is built for Windows, Linux, and OS X, and that unit/sanity tests are run automatically.

Manual Quality Assurance (QA) Testing

Changes should be tested by somebody other than the developer who wrote the code. This is especially important for large or high-risk changes. It is useful to add a test plan to the pull request description if testing the changes is not straightforward.

Translations

Changes to translations as well as new translations can be submitted to Bitcoin Core's Transifex page.

Translations are periodically pulled from Transifex and merged into the git repository. See the translation process for details on how this works.

Important: We do not accept translation changes as GitHub pull requests because the next pull from Transifex would automatically overwrite them again.

Translators should also subscribe to the mailing list.