zcash-hackworks
/
bitcoin
mirror of https://github.com/zcash-hackworks/bitcoin.git
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
3,302 Commits 9 Branches 176 Tags 87 MiB
C++ 64.8%
Python 14.7%
C 13.8%
M4 2.5%
Makefile 1.5%
Other 2.6%
Go to file
Jeff Garzik fcf234fc08 RPC: HTTP server uses its own ReadHTTPRequestLine() 
rather than reusing ReadHTTPStatus() from the client mode.

The following additional HTTP request validations are added, both in line with
existing HTTP client practice:

1) HTTP method must be GET or POST.  Most clients use POST, some
   use GET.  Either way, this continues to work.
2) HTTP URI must start with "/" character.
   Normal URI is "/" (a 1-char string), so this is fine.
 		2012-11-04 17:16:46 -05:00
contrib Merge pull request #1967 from TheBlueMatt/leveldbmakefile 2012-10-29 14:11:55 -07:00
doc Upgrade to Qt 4.8.3 (because 4.8.2 was removed from qt repos?) 2012-10-29 15:43:18 -04:00
share Update version numbers to 0.7.99 2012-10-21 12:10:08 +02:00
src RPC: HTTP server uses its own ReadHTTPRequestLine() 2012-11-04 17:16:46 -05:00
.gitattributes Build identification strings 2012-04-10 18:16:53 +02:00
.gitignore Import LevelDB 1.5, it will be used for the transaction database. 2012-10-20 23:08:56 +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
bitcoin-qt.pro Use && instead of ; in leveldb calls to makefile. 2012-10-29 15:43:17 -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.