< contrapumpkin> what were the origins of the OP_CHECKMULTISIG bug? was it a misunderstanding or a typo or what?
< sipa> you'll have to ask satoshi
< * contrapumpkin> calls him up
< arubi> that's nothing compared to the sighash single bug, where you sign a value called "one", it looks like "one", and it ends up being 2^248 :P
< sipa> or the "concatenate scriptPubKey and scriptSig before execution" joke :)
< gmaxwell> As if we didn't have other reasons to want to move off of github, geesh:
< gmaxwell> 12:30:03 < spudowiar> I did some GitHub trolling (because he was saying that Jimmy Song contributed to BCH because they cherry-picked his commit) :P https://github.com/bitcoin/bitcoin/commit/07815c08af49320454701dbe2e088540956bd049
< gmaxwell> apparently those URLs will show commits from any forks.
< gmaxwell> so anyone who wants to could form a commit that looked like it was from any of us, and link to it in our repository.
< contrapumpkin> yeah, that's confused several people in different communities I've seen
< contrapumpkin> I suppose the github claim is that if you care, you should look for the branch/tag marker under the commit message, but who's going to notice that
< sipa> it would be nice to have a setting on github that it won't show your name (or at least not link to your profile) on any commits that you haven't GPG signed
< TD-Linux> yeah. in fact it'd be nice if you could totally bypass its normal email verification method, or not use emails in git commits at all when doing so.
< sipa> right
< pincode_> yep
< bitcoin-git> [bitcoin] cryptonexii opened pull request #12236: Latest windows build instructions (master...patch-1) https://github.com/bitcoin/bitcoin/pull/12236
< bitcoin-git> [bitcoin] cryptonexii closed pull request #12236: Latest windows build instructions (master...patch-1) https://github.com/bitcoin/bitcoin/pull/12236