q3k
/
primeminer
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity
2,016 Commits
1 Branch
0 Tags
22 MiB
C++ 79.7%
C 10.5%
Python 3.3%
HTML 2.4%
QMake 1.3%
Other 2.7%
 
 
 
 
 
 
Go to file
Pieter Wuille a20c0d0f67 Build identification strings 
All client version information is moved to version.cpp, which optionally
(-DHAVE_BUILD_INFO) includes build.h. build.h is automatically generated
on supporting platforms via contrib/genbuild.sh, using git describe.

The git export-subst attribute is used to put the commit id statically
in version.cpp inside generated archives, and this value is used if no
build.h is present.

The gitian descriptors are modified to use git archive instead of a
copy, to create the src/ directory in the output. This way,
src/src/version.cpp will contain the static commit id. To prevent
gitian builds from getting the "-dirty" marker in their git-describe
generated identifiers, no touching of files or running sed on the
makefile is performed anymore. This does not seem to influence
determinism.
 		2012-04-10 18:16:53 +02:00
contrib Build identification strings 2012-04-10 18:16:53 +02:00
doc Build identification strings 2012-04-10 18:16:53 +02:00
scripts/qt move qt-specific scripts to qt-specific directory in scripts/ 2011-09-18 12:44:32 +02:00
share Build identification strings 2012-04-10 18:16:53 +02:00
src Build identification strings 2012-04-10 18:16:53 +02:00
.gitattributes Build identification strings 2012-04-10 18:16:53 +02:00
.gitignore Build identification strings 2012-04-10 18:16:53 +02:00
COPYING Update all copyrights to 2012 2012-02-07 11:28:30 -05:00
INSTALL Update build instructions for the new, no-wxwidgets world 2011-09-26 11:40:43 -04:00
README directory re-organization (keeps the old build system) 2011-04-23 12:10:25 +02:00
README.md Updated readme file with timers. 2011-09-26 22:22:19 -04:00
bitcoin-qt.pro Build identification strings 2012-04-10 18:16:53 +02:00

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 mailing list: http://sourceforge.net/mailarchive/forum.php?forum_name=bitcoin-development

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, but is not guaranteed to be completely stable. Tags are regularly created to indicate new official, stable release versions of Bitcoin. If you would like to help test the Bitcoin core, please contact QA@BitcoinTesting.org.

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

From time to time a pull request will become outdated. If this occurs, and the pull is no longer automatically mergeable; a comment on the pull will be used to issue a warning of closure. The pull will be closed 15 days after the warning if action is not taken by the author. Pull requests closed in this manner will have their corresponding issue labeled 'stagnant'.

Issues with no commits will be given a similar warning, and closed after 15 days from their last activity. Issues closed in this manner will be labeled 'stale'.

Requests to reopen closed pull requests and/or issues can be submitted to QA@BitcoinTesting.org.