neobytes-project/neobytes
neobytes-project/neobytes
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity
Neobytes - Reinventing Cryptocurrency https://neobytes.network/
3,122 Commits 3 Branches 0 Tags 185 MiB
C++ 62.3%
C 19.5%
Python 8.4%
Assembly 5%
M4 1.8%
Other 2.8%
50e01ee620
Go to file
xanatos 50e01ee620 toHTML won't add empty wtx.mapValue elements 
As the code was before, toHTML added empty elements to mapValue to check for their existance. Now first it check for their existance and then for their non-emptiness.

Removed a duplicated identical if

There are two equal ifs, one inside another. If the first one is true, then the second one is true.
2012-09-28 15:50:48 +02:00
contrib Merge pull request #1803 from luke-jr/md2k7_license 2012-09-09 01:58:00 -07:00
doc Update Bugreport Links 2012-09-22 18:05:25 +08:00
share Bump client version number for 0.7.0rc3 2012-09-12 14:07:22 -04:00
src toHTML won't add empty wtx.mapValue elements 2012-09-28 15:50:48 +02:00
.gitattributes Build identification strings 2012-04-10 18:16:53 +02:00
.gitignore Update gitignore and Makefiles for build.h move from src/ to src/obj 2012-09-20 10:28:13 -04:00
bitcoin-qt.pro Remove -Wformat* warnings from makefiles 2012-09-27 04:10:21 +02:00
COPYING Update all copyrights to 2012 2012-02-07 11:28:30 -05:00
INSTALL Update master 2012-06-21 09:36:20 +08: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

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.