1 2017-12-03 00:56:23 0|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ââ¬Â¦
2 2017-12-03 01:04:52 0|luke-jr|bitmangw: start on non-consensus code. reviewing open PRs and writing tests are typically a good place.
3 2017-12-03 01:06:39 0|bitmangw|thanks luke-jr
4 2017-12-03 03:48:10 0|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."
5 2017-12-03 03:48:51 0|karelb|Hey it was me
6 2017-12-03 03:48:52 0|karelb|sorry
7 2017-12-03 03:49:00 0|karelb|I didn't know people will start seeing this
8 2017-12-03 03:49:03 0|karelb|I will delete the commit
9 2017-12-03 03:49:52 0|karelb|hm... I cannot delete the commit though
10 2017-12-03 03:49:59 0|karelb|I deleted the branch, but the commit is still there :(
11 2017-12-03 03:59:17 0|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 :)
12 2017-12-03 04:01:47 0|karelb|It's more concerning you can actually view the file and it seems like it is on the repo
13 2017-12-03 04:01:49 0|karelb|https://github.com/bitcoin/bitcoin/blob/ca5e41d2ec841a45a3109452076ef205e9c956b8/README.md
14 2017-12-03 04:01:53 0|kanzure|well at least the object doesn't show up in "git fetch".. (would be easy to spam large files)
15 2017-12-03 04:02:31 0|karelb|so someone can post "fake guidelines" that way, or link to malware binaries
16 2017-12-03 04:02:55 0|karelb|and it looks genuine
17 2017-12-03 04:03:20 0|kanzure|please email support@github.com
18 2017-12-03 04:03:27 0|karelb|I did
19 2017-12-03 10:01:02 0|meshcollider|Heh I saw the LOVE LOVE LOVE commit title and thought this was going to be good, it didn't disappoint ;)
20 2017-12-03 10:01:15 0|meshcollider|That's an interesting bug
21 2017-12-03 10:07:36 0|sheepmolestor|hi meshcollider
22 2017-12-03 10:07:45 0|sheepmolestor|im a fan
23 2017-12-03 10:08:21 0|meshcollider|sheepmolestor: thanks but not the place :)
24 2017-12-03 19:59:20 0|BlueMatt|cfields: re: #11799 did we decide LOCKS_EXCLUDED was useless?
25 2017-12-03 19:59:21 0|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
26 2017-12-03 19:59:41 0|BlueMatt|does it even enforce if you do a LOCK(cs) call_function_with_cs_excluded(); back-to-back?
27 2017-12-03 22:02:37 0|vicenteH|is branch 0.15 in source code a stable one?
28 2017-12-03 22:13:21 0|sipa|vicenteH: yes
29 2017-12-03 22:13:36 0|sipa|it only gets bugfixes/backports from master