Bitcoin to NYC3 and update gitian compile code
This commit is contained in:
@@ -1,6 +1,6 @@
|
||||
<!-- This issue tracker is only for technical issues related to Bitcoin Core.
|
||||
<!-- This issue tracker is only for technical issues related to NYC3 Core.
|
||||
|
||||
General bitcoin questions and/or support requests are best directed to the Bitcoin StackExchange at https://bitcoin.stackexchange.com.
|
||||
General bitcoin questions and/or support requests are best directed to the NYC3 StackExchange at https://bitcoin.stackexchange.com.
|
||||
|
||||
For reporting security issues, please read instructions at https://bitcoincore.org/en/contact/.
|
||||
|
||||
@@ -13,7 +13,7 @@ If the node is "stuck" during sync or giving "block checksum mismatch" errors, p
|
||||
|
||||
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
|
||||
|
||||
<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
|
||||
<!-- What version of NYC3 Core are you using, where did you get it (website, self-compiled, etc)? -->
|
||||
|
||||
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
|
||||
|
||||
|
||||
@@ -2,7 +2,7 @@ Pull requests without a rationale and clear improvement may be closed
|
||||
immediately.
|
||||
|
||||
Please provide clear motivation for your patch and explain how it improves
|
||||
Bitcoin Core user experience or Bitcoin Core developer experience
|
||||
NYC3 Core user experience or NYC3 Core developer experience
|
||||
significantly.
|
||||
|
||||
* Any test improvements or new tests that improve coverage are always welcome.
|
||||
@@ -15,7 +15,7 @@ significantly.
|
||||
was fixed.
|
||||
* Features are welcome, but might be rejected due to design or scope issues.
|
||||
If a feature is based on a lot of dependencies, contributors should first
|
||||
consider building the system outside of Bitcoin Core, if possible.
|
||||
consider building the system outside of NYC3 Core, if possible.
|
||||
* Refactoring changes are only accepted if they are required for a feature or
|
||||
bug fix or otherwise improve developer experience significantly. For example,
|
||||
most "code style" refactoring changes require a thorough explanation why they
|
||||
@@ -25,7 +25,7 @@ significantly.
|
||||
preferred in the [developer notes](/doc/developer-notes.md), stylistic code
|
||||
changes are usually rejected.
|
||||
|
||||
Bitcoin Core has a thorough review process and even the most trivial change
|
||||
NYC3 Core has a thorough review process and even the most trivial change
|
||||
needs to pass a lot of eyes and requires non-zero or even substantial time
|
||||
effort to review. There is a huge lack of active reviewers on the project, so
|
||||
patches often sit for a long time.
|
||||
|
||||
Reference in New Issue
Block a user