diff options
| author | fanquake <fanquake@gmail.com> | 2019-10-24 11:12:12 -0400 |
|---|---|---|
| committer | fanquake <fanquake@gmail.com> | 2019-10-24 11:36:25 -0400 |
| commit | d7134ead84e3b824688f0ba195d5dc461a0491e6 (patch) | |
| tree | 30febe10a8d843ee38771e60bac235d5071374f5 /.github | |
| parent | d53828cb79688d72a18d2cc550dcd1dfe2d3dd85 (diff) | |
| parent | 6f6852335fc236dd6ec161162f49bfd813036acc (diff) | |
Merge #17239: doc: Changed miniupnp links to https
6f6852335fc236dd6ec161162f49bfd813036acc doc: Changed miniupnp links to https (Marius Kjærstad)
Pull request description:
doc: Changed miniupnp links to https
ACKs for top commit:
fjahr:
ACK 6f68523
fanquake:
ACK 6f6852335fc236dd6ec161162f49bfd813036acc - as mentioned in this [comment](https://github.com/bitcoin/bitcoin/pull/17166#issuecomment-545906845), in future, there's no need to open a new PR instead than squashing. One of the requirements of contributing to Bitcoin Core is some basic `git` usage, and we have some documentation on that in our [CONTRIBUTING.md](https://github.com/bitcoin/bitcoin/blob/master/CONTRIBUTING.md#squashing-commits) (which also mentions not to open multiple PRs).
Tree-SHA512: 1e806326552b94dc1c2f105bed822a1dd56127d42bbb0c15a16623ff084b2047331f2f1ad5303c99b0d68c70ad2caf8e8028eb354ba4379973b9e1198676ce72
Diffstat (limited to '.github')
0 files changed, 0 insertions, 0 deletions