sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-29 13:59:06 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

Merge #7975: [doc] Update bitcoin-core GitHub links

Browse Source 
faf3d11 [doc] Update bitcoin-core GitHub links (MarcoFalke)
This commit is contained in:
Wladimir J. van der Laan 2016-05-04 14:28:12 +02:00
commit fc23fee690
No known key found for this signature in database
GPG Key ID: 74810B012346C9A6
6 changed files with 12 additions and 12 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
contrib/devtools/README.md
View File

@ -48,9 +48,9 @@ the commit it claims to have been updated to.
To use, make sure that you have fetched the upstream repository branch in which the subtree is To use, make sure that you have fetched the upstream repository branch in which the subtree is
maintained: maintained:
* for `src/secp256k1`: https://github.com/bitcoin/secp256k1.git (branch master) * for `src/secp256k1`: https://github.com/bitcoin-core/secp256k1.git (branch master)
* for `src/leveldb`: https://github.com/bitcoin/leveldb.git (branch bitcoin-fork) * for `src/leveldb`: https://github.com/bitcoin-core/leveldb.git (branch bitcoin-fork)
* for `src/univalue`: https://github.com/bitcoin/univalue.git (branch master) * for `src/univalue`: https://github.com/bitcoin-core/univalue.git (branch master)
Usage: `git-subtree-check.sh DIR COMMIT` Usage: `git-subtree-check.sh DIR COMMIT`

2
contrib/gitian-descriptors/gitian-osx-signer.yml
View File

@ -8,7 +8,7 @@ packages:
- "faketime" - "faketime"
reference_datetime: "2016-01-01 00:00:00" reference_datetime: "2016-01-01 00:00:00"
remotes: remotes:
- "url": "https://github.com/bitcoin/bitcoin-detached-sigs.git" - "url": "https://github.com/bitcoin-core/bitcoin-detached-sigs.git"
"dir": "signature" "dir": "signature"
files: files:
- "bitcoin-osx-unsigned.tar.gz" - "bitcoin-osx-unsigned.tar.gz"

2
contrib/gitian-descriptors/gitian-win-signer.yml
View File

@ -9,7 +9,7 @@ packages:
- "autoconf" - "autoconf"
reference_datetime: "2016-01-01 00:00:00" reference_datetime: "2016-01-01 00:00:00"
remotes: remotes:
- "url": "https://github.com/bitcoin/bitcoin-detached-sigs.git" - "url": "https://github.com/bitcoin-core/bitcoin-detached-sigs.git"
"dir": "signature" "dir": "signature"
files: files:
- "osslsigncode-1.7.1.tar.gz" - "osslsigncode-1.7.1.tar.gz"

6
doc/gitian-building.md
View File

@ -310,7 +310,7 @@ Clone the git repositories for bitcoin and Gitian.
```bash ```bash
git clone https://github.com/devrandom/gitian-builder.git git clone https://github.com/devrandom/gitian-builder.git
git clone https://github.com/bitcoin/bitcoin git clone https://github.com/bitcoin/bitcoin
git clone https://github.com/bitcoin/gitian.sigs.git git clone https://github.com/bitcoin-core/gitian.sigs.git
``` ```
Setting up the Gitian image Setting up the Gitian image
@ -441,7 +441,7 @@ Then when building, override the remote URLs that gbuild would otherwise pull fr
```bash ```bash
cd /some/root/path/ cd /some/root/path/
git clone https://github.com/bitcoin/bitcoin-detached-sigs.git git clone https://github.com/bitcoin-core/bitcoin-detached-sigs.git
BTCPATH=/some/root/path/bitcoin.git BTCPATH=/some/root/path/bitcoin.git
SIGPATH=/some/root/path/bitcoin-detached-sigs.git SIGPATH=/some/root/path/bitcoin-detached-sigs.git
@ -473,5 +473,5 @@ Uploading signatures
--------------------- ---------------------
After building and signing you can push your signatures (both the `.assert` and `.assert.sig` files) to the After building and signing you can push your signatures (both the `.assert` and `.assert.sig` files) to the
[bitcoin/gitian.sigs](https://github.com/bitcoin/gitian.sigs/) repository, or if that's not possible create a pull [bitcoin-core/gitian.sigs](https://github.com/bitcoin-core/gitian.sigs/) repository, or if that's not possible create a pull
request. You can also mail the files to Wladimir (laanwj@gmail.com) and he will commit them. request. You can also mail the files to Wladimir (laanwj@gmail.com) and he will commit them.

2
doc/release-notes/release-notes-0.12.0.md
View File

@ -61,7 +61,7 @@ Signature validation using libsecp256k1
--------------------------------------- ---------------------------------------
ECDSA signatures inside Bitcoin transactions now use validation using ECDSA signatures inside Bitcoin transactions now use validation using
[libsecp256k1](https://github.com/bitcoin/secp256k1) instead of OpenSSL. [libsecp256k1](https://github.com/bitcoin-core/secp256k1) instead of OpenSSL.
Depending on the platform, this means a significant speedup for raw signature Depending on the platform, this means a significant speedup for raw signature
validation speed. The advantage is largest on x86_64, where validation is over validation speed. The advantage is largest on x86_64, where validation is over

6
doc/release-process.md
View File

@ -20,8 +20,8 @@ Before every major release:
Check out the source code in the following directory hierarchy. Check out the source code in the following directory hierarchy.
cd /path/to/your/toplevel/build cd /path/to/your/toplevel/build
git clone https://github.com/bitcoin/gitian.sigs.git git clone https://github.com/bitcoin-core/gitian.sigs.git
git clone https://github.com/bitcoin/bitcoin-detached-sigs.git git clone https://github.com/bitcoin-core/bitcoin-detached-sigs.git
git clone https://github.com/devrandom/gitian-builder.git git clone https://github.com/devrandom/gitian-builder.git
git clone https://github.com/bitcoin/bitcoin.git git clone https://github.com/bitcoin/bitcoin.git
@ -170,7 +170,7 @@ Commit your signature to gitian.sigs:
Wait for Windows/OS X detached signatures: Wait for Windows/OS X detached signatures:
- Once the Windows/OS X builds each have 3 matching signatures, they will be signed with their respective release keys. - Once the Windows/OS X builds each have 3 matching signatures, they will be signed with their respective release keys.
- Detached signatures will then be committed to the [bitcoin-detached-sigs](https://github.com/bitcoin/bitcoin-detached-sigs) repository, which can be combined with the unsigned apps to create signed binaries. - Detached signatures will then be committed to the [bitcoin-detached-sigs](https://github.com/bitcoin-core/bitcoin-detached-sigs) repository, which can be combined with the unsigned apps to create signed binaries.
Create (and optionally verify) the signed OS X binary: Create (and optionally verify) the signed OS X binary: