< hebasto> Travis returns ERROR: An error occured while trying to fetch your .travis.yml file. Could someone restart Travis on #14250.
< gribble> https://github.com/bitcoin/bitcoin/issues/14250 | qt: Remove redundant stopThread() and stopExecutor() signals by hebasto · Pull Request #14250 · bitcoin/bitcoin · GitHub
< bitcoin-git> [bitcoin] MarcoFalke closed pull request #14250: qt: Remove redundant stopThread() and stopExecutor() signals (master...stopthread-signal) https://github.com/bitcoin/bitcoin/pull/14250
< hebasto> MarcoFalke: thanks
< bitcoin-git> [bitcoin] Empact opened pull request #15114: Qt: Replace remaining 0 with nullptr (master...qt-zero-as-null-pointer-constant) https://github.com/bitcoin/bitcoin/pull/15114
< tryphe> nullptr shouldn't be used instead of 0. to be platform independent, it should be Q_NULLPTR (which is null on some platforms and nullptr on others)
< tryphe> in the context of the Qt pull 15114
< luke-jr> tryphe: nullptr is standard C++, which is a requirement for Bitcoin Core
< luke-jr> that being said.. gratuitous changes like this for no reason are not really useful
< tryphe> luke-jr, it's c++11 standard, which is not the only compiler supported by Qt
< luke-jr> tryphe: it is the only compiler standard supported by Bitcoin Core
< tryphe> luke-jr, makes sense i guess
< tryphe> luke-jr, or just leave it 0 =p
< luke-jr> yes, it can be updated when someone has reason to touch those lines
< tryphe> hebasto: thanks, i guess they did get rid of null support then
< bitcoin-git> [bitcoin] luke-jr opened pull request #15115: GUI: Replace send-to-self with dual send+receive entries (master...rm_send2self) https://github.com/bitcoin/bitcoin/pull/15115
< bitcoin-git> [bitcoin] practicalswift opened pull request #15117: Fix out-of-bounds write in case of failing mmap(...) in PosixLockedPageAllocator::AllocateLocked (master...gracefully-handle-mmap-failure) https://github.com/bitcoin/bitcoin/pull/15117
< hebasto> How can I increase connected peers number on testnet3?
< promag> hebasto: https://github.com/bitcoin/bitcoin/pull/15115#issuecomment-451763152 really? I'll revisit that one
< luke-jr> hebasto: pretty sure promag meant #12578 *combined with* #15115
< gribble> https://github.com/bitcoin/bitcoin/issues/12578 | gui: Add transaction record type Fee by promag · Pull Request #12578 · bitcoin/bitcoin · GitHub
< gribble> https://github.com/bitcoin/bitcoin/issues/15115 | GUI: Replace send-to-self with dual send+receive entries by luke-jr · Pull Request #15115 · bitcoin/bitcoin · GitHub
< hebasto> promag: on screenshots "Payment to yourself" transactions show "(n/a)" w/o "Fee" row.
< promag> hebasto: have you combined both branches?
< hebasto> promag: will try
< luke-jr> note: it's not trivial
< luke-jr> (but definitely doable - I actually rebased 15115 off a branch that had 12578 already :P)
< hebasto> luke-jr: thanks
< promag> luke-jr: for knots?
< luke-jr> promag: no, for something else (which has other stuff touching this code too)
< howdyhow> hi everyone
< howdyhow> its taking too long to transfer my bitcore to sychronise so i have extracted the the private key in console but then put it into my block chain acccount but its still sayingits unspendable
< harding> howdyhow: this channel is for development, please use #bitcoin for support.
< howdyhow> thanks friend