< BlueMatt> sipa: please do not rebase your prs when you squash things unless there are conflicts....makes diff-tree very hard to use to verify changes
< fanquake> wumpus which version of qt is used in the bitocin-qt your testing for memory leaks?
< bitcoin-git> [bitcoin] ShamimLike opened pull request #9193: Update copyright year to 2016 (master...patch-1) https://github.com/bitcoin/bitcoin/pull/9193
< instagibbs> BlueMatt, on that note, does github expose and easy way to figure out previous commit hashes post-squash? I come back to PRs and don't see a way of grabbing history
< instagibbs> gitlab leaves a nice commit trail
< BlueMatt> ;;later tell instagibbs not as far as I'm aware...you're aware of https://gist.github.com/piscisaureus/3342247, right? I use my local copy to see what version i reviewed
< gribble> The operation succeeded.
< bitcoin-git> [bitcoin] instagibbs opened pull request #9194: Add flags to getrawtransaction and getblock to return non-segwit seri… (master...nonswserialrpc) https://github.com/bitcoin/bitcoin/pull/9194
< instagibbs> BlueMatt, thanks, I know that, but I guess the answer is "always grab the latest copy of what you're reviewing"