< bitmangw> Hello .. just got here… any pointers .. links on where to start ? I have been devloping in C/C++ for a while now.. and on most platforms…
< luke-jr> bitmangw: start on non-consensus code. reviewing open PRs and writing tests are typically a good place.
< bitmangw> thanks luke-jr
< kanzure> "Note: This is actually only on my fork, but github displays as if it was on the main repository. It's a github bug."
< karelb> Hey it was me
< karelb> sorry
< karelb> I didn't know people will start seeing this
< karelb> I will delete the commit
< karelb> hm... I cannot delete the commit though
< karelb> I deleted the branch, but the commit is still there :(
< karelb> well I can't do anything now. Sorry again, it was a joke from my part, I didn't think it will actually work :)
< karelb> It's more concerning you can actually view the file and it seems like it is on the repo
< kanzure> well at least the object doesn't show up in "git fetch".. (would be easy to spam large files)
< karelb> so someone can post "fake guidelines" that way, or link to malware binaries
< karelb> and it looks genuine
< kanzure> please email support@github.com
< karelb> I did
< meshcollider> Heh I saw the LOVE LOVE LOVE commit title and thought this was going to be good, it didn't disappoint ;)
< meshcollider> That's an interesting bug
< sheepmolestor> hi meshcollider
< sheepmolestor> im a fan
< meshcollider> sheepmolestor: thanks but not the place :)
< BlueMatt> cfields: re: #11799 did we decide LOCKS_EXCLUDED was useless?
< gribble> https://github.com/bitcoin/bitcoin/issues/11799 | wallet: Add compile-time checking of (non-)locking assumptions for BlockUntilSyncedToCurrentChain() [wip] by practicalswift · Pull Request #11799 · bitcoin/bitcoin · GitHub
< BlueMatt> does it even enforce if you do a LOCK(cs) call_function_with_cs_excluded(); back-to-back?
< vicenteH> is branch 0.15 in source code a stable one?
< sipa> vicenteH: yes
< sipa> it only gets bugfixes/backports from master