Kevacoin source tree
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
 
 
 
 
 
 
tcatm d12ea887bc disable -daemon on windows; bitcoind forks only with -daemon set 14 years ago
contrib
cryptopp
json
locale [locale] Regenerate es, nl binary message catalogs 14 years ago
obj
rc
xpm
.gitignore
README.md
base58.h
bignum.h
build-msw.txt
build-osx.txt
build-unix.txt
coding.txt
db.cpp Fix deadlocks in setaccount, sendfrom RPC calls 14 years ago
db.h
headers.h
init.cpp disable -daemon on windows; bitcoind forks only with -daemon set 14 years ago
init.h
irc.cpp
irc.h
key.h
license.txt
main.cpp Fix deadlocks in setaccount, sendfrom RPC calls 14 years ago
main.h sendmany RPC command, to send to multiple recipients in one transaction. 14 years ago
makefile.mingw
makefile.osx
makefile.unix
makefile.vc
net.cpp Update DNS seed list 14 years ago
net.h Merge branch 'shy' 14 years ago
noui.h
rpc.cpp rfc1123Time: increase buffer size for time string 14 years ago
rpc.h
script.cpp
script.h
serialize.h
setup.nsi
sha256.cpp
strlcpy.h
ui.cpp disable -daemon on windows; bitcoind forks only with -daemon set 14 years ago
ui.h
ui.rc
uibase.cpp Update copyright in About box from 2010 to 2011 14 years ago
uibase.h
uint256.h
uiproject.fbp Update copyright in About box from 2010 to 2011 14 years ago
util.cpp Fix -logtimestamps to only print time prefix once per output line 14 years ago
util.h Fix -logtimestamps to only print time prefix once per output line 14 years ago

README.md

Bitcoin integration/staging tree

Development process

Developers work in their own trees, then submit pull requests when they think their feature or bug fix is ready.

If it is a simple/trivial/non-controversial change, then one of the bitcoin development team members simply pulls it.

If it is a more complicated or potentially controversial change, then the patch submitter will be asked to start a discussion (if they haven't already) on the development forums: http://www.bitcoin.org/smf/index.php?board=6.0 The patch will be accepted if there is broad consensus that it is a good thing. Developers should expect to rework and resubmit patches if they don't match the project's coding conventions (see coding.txt) or are controversial.

The master branch is regularly built and tested (by who? need people willing to be quality assurance testers), and periodically pushed to the subversion repo to become the official, stable, released bitcoin.

Feature branches are created when there are major new features being worked on by several people.