sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-24 11:32:46 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

dashify productivity.md

Browse Source 
Signed-off-by: pasta <pasta@dashboost.org>
This commit is contained in:
pasta 2021-07-10 12:10:07 -05:00
parent 26d618df99
commit ff23880053
1 changed files with 4 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

8
doc/productivity.md
View File

@ -73,9 +73,9 @@ When rebuilding during development, note that running `make`, without giving a t
Obviously, it is important to build and run the tests at appropriate times -- but when you just want a quick compile to check your work, consider picking one or a set of build targets relevant to what you're working on, e.g.:
```sh
make src/bitcoind src/bitcoin-cli
make src/qt/bitcoin-qt
make -C src bitcoin_bench
make src/dashd src/dash-cli
make src/qt/dash-qt
make -C src dash_bench
```
(You can and should combine this with `-j`, as above, for a parallel build.)
@ -173,7 +173,7 @@ When looking at other's pull requests, it may make sense to add the following se
```
[remote "upstream-pull"]
fetch = +refs/pull/*:refs/remotes/upstream-pull/*
url = git@github.com:bitcoin/bitcoin.git
url = git@github.com:dashpay/dash.git
```
This will add an `upstream-pull` remote to your git repository, which can be fetched using `git fetch --all` or `git fetch upstream-pull`. Afterwards, you can use `upstream-pull/NUMBER/head` in arguments to `git show`, `git checkout` and anywhere a commit id would be acceptable to see the changes from pull request NUMBER.