< bitcoin-git>
[bitcoin] ch4ot1c opened pull request #17005: build: Qt version appears only if GUI is being built (master...build/qt-no) https://github.com/bitcoin/bitcoin/pull/17005
< bitcoin-git>
bitcoin/master 3eea6a8 Emil Engler: refactor: Remove Qt function to disable menu icons on macOS
< bitcoin-git>
bitcoin/master b0e268d fanquake: Merge #16969: refactor: Remove Qt function to disable menu icons on macOS
< bitcoin-git>
[bitcoin] fanquake merged pull request #16969: refactor: Remove Qt function to disable menu icons on macOS (master...2019-09-refactor-qt-menuicons-macos) https://github.com/bitcoin/bitcoin/pull/16969
< warren>
MarcoFalke: question about https://github.com/bitcoin/bitcoin/pull/15845 Would it be possible after this, your bitcoind node could sync with filters, prune while saving the those older filters, then you'd be able to rescan your own wallet from your your own filters?
< luke-jr>
is there a reason we haven't bumped libsecp256k1 in >2 years?
< bitcoin-git>
bitcoin/master 57b0cd4 Jon Layton: build: Installed Qt version only appears if being built
< bitcoin-git>
bitcoin/master 52acd24 fanquake: Merge #17005: build: Qt version appears only if GUI is being built
< bitcoin-git>
[bitcoin] fanquake merged pull request #17005: build: Qt version appears only if GUI is being built (master...build/qt-no) https://github.com/bitcoin/bitcoin/pull/17005
< emilengler>
When I open a PR as a fix for both, v0.19 and master, how should I do this?
< emilengler>
With 2 Prs?
< emilengler>
Or is this a job for the maintainers?
< provoostenator>
emilengler: start with master. It will get marked for back port, which you or someone else can make a PR for after the master one ismerged.
< provoostenator>
We haven't branched v0.19 yet, so in this case your PR only needs to be for master.
< jonatack>
emilengler: seconding what provoostenator wrote, git tag -n | sort -V shows you the latest tag which ATM is v0.18.1