diff options
| author | fanquake <fanquake@gmail.com> | 2019-10-20 11:52:02 -0400 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2019-10-20 12:04:09 -0400 |
| commit | b8f041af2d2c89afdc14f8c632dfb7fecb535cb5 (patch) | |
| tree | ebba2ad3b6be6f3d2f1889247bdfef85b5509faa /depends/config.sub | |
| parent | b6e34afe9735faf97d6be7a90fafd33ec18c0cbb (diff) | |
| parent | f09ba060cacd42e4cb9a242c1d731deb1f6623c6 (diff) | |
| download | bitcoin-b8f041af2d2c89afdc14f8c632dfb7fecb535cb5.tar.xz | |
Merge #17157: doc: Added instructions for how to add an upsteam to forked repo
f09ba060cacd42e4cb9a242c1d731deb1f6623c6 doc: Added instructions for how to add an upsteam to forked repo (dannmat)
Pull request description:
As a first time git developer, I struggled to understand whether to create a new fork for each pull request or not.
After asking the IRC chat, I have added this to the documentation to further help new developers using git.
ACKs for top commit:
fanquake:
ACK f09ba060cacd42e4cb9a242c1d731deb1f6623c6 - For such a simple change, I think we've bike-shed this enough already. The `bitcoin/bitcoin` repo isn't really where anyone should be learning how to use `git` etc, but I think linking out here is ok.
Tree-SHA512: e0e9d655d0725e0128673afedb81dc5ba9387968fcbb681de7e50155a2cfa1a7f39fad040b596f4de9ad6727a1a8a90fd3d36eaa5242bc12186c3b82abd23fb2
Diffstat (limited to 'depends/config.sub')
0 files changed, 0 insertions, 0 deletions