log☇︎
16600+ entries in 0.026s
mod6: genesis.vpatch (asciilifeform, mircea_popescu, mod6, trinque)
mod6: which currently stands at 4 lords at this point
mod6: well, you press out genesis if you trust at least one person who has signed it.
mod6: so if i get hit by a bus, and alf has signed all the patches, then you're ok as long as you trust alfie. or vice versa.
mod6: it should do what these guys were talking about before, just press up to level where key you trust has signed.
mod6: oh aight
mod6: i thought ben_vulpes made a lisp deal?
mod6: Thanks!
mod6: tax payment to the Foundation.
mod6: I, jurov, am hereby submitting the treasurer's reward in full as my
mod6: i kindof agree.
mod6: so shiva part 1 & part 2 + shiva fix.
mod6: i think there is some confusion there. as you saw in the logs.
mod6: so even though I was able to press out shiva, et. al.; it might be worthwhile to make a list of which patches need to be included to make it work.
mod6: now we get to it.
mod6: ahhhhhhh
mod6: well, they're your things!
mod6: asciilifeform: cool with you if i send those re-worked patches to the ML?
mod6: there is some good Q&A in the comments.
mod6: *cough*3rd time*cough*
mod6: <+mircea_popescu> ben_vulpes mod6 if teh esteemed foundation'd give an opinion on http://trilema.com/2016/the-necessary-prerequisite-for-any-change-to-the-bitcoin-protocol/ kthx. << I'm reading through the post, must grok.
mod6: and a similar situation in V would be like 69 patches to patch the original patch.
mod6: ascii_butugychag: one fix every now and then isn't horrible or anything, id just hate to see the situation (like at usg-like job) where people create a turd, create a PR, and then have to keep chainging the PR until "ready"
mod6: thanks trinque
mod6: plzkthx
mod6: someone up ascii_butugychag
mod6: i must be stale ascii_butugychag
mod6: !up ascii_butugychag
mod6: ascii_butugychag: take a look at these and let me know what you think, plz: http://dpaste.com/0P9PR2S.txt && http://dpaste.com/2SV1RKB.txt
mod6: so that looks like its doing the right thing, and the log was updated as well.
mod6: "version" : 99998,
mod6: root 31948 0.0 0.0 8924 708 pts/7 S+ 19:04 0:00 grep --colour=auto bitcoind
mod6: root 31936 32.1 37.8 1741912 1453164 pts/7 SLl 19:01 0:55 ./bitcoind -datadir=/mnt/btc-dev/.bitcoin -myip=127.0.0.1 -addnode=188.68.240.159 -setverstring=trb -setvernum=99998 -lows
mod6: # ps aux | grep bitcoind && LC_ALL=C ./bitcoind -datadir=/mnt/btc-dev/.bitcoin getinfo | grep version
mod6: compiled just fine, just kicked it off for a quick test...
mod6: anyway, i created a new patch for PVS and did a regrind on malleus (since this one depends on main.cpp)
mod6: probably was just going to fast.
mod6: hey ascii_butugychag, so i figured out what my dumbass did yesterday. somehow, when looking at your fix patch - I missed the portion where you changed main.cpp altogether.
mod6: !up ascii_butugychag
mod6: ok will look again at it tomorrow. thanks ascii, g'night!
mod6: i'll see if i can figure out wtf I did differently tomorrow.
mod6: there is supposed to be a line break up here ^ but didn't translate through the copy
mod6: looks good
mod6: 22900 pts/1 S+ 0:00 grep --colour=auto bitcoind "version" : 99998,
mod6: 22877 pts/1 SLl 0:54 ./bitcoind -datadir=/mnt/btc-dev/.bitcoin -myip=127.0.0.1 -addnode=188.68.240.159 -setverstring=trb -setvernum=99998
mod6: # ps ax | grep bitcoind && LC_ALL=C ./bitcoind -datadir=/mnt/btc-dev/.bitcoin getinfo | grep version
mod6: gonna check getinfo in a sec.
mod6: so far, this is good.
mod6: <+asciilifeform> counting to what, zero ? << it did show in the log already when i started with -setvernum=99998
mod6: Bitcoin version 0.9.99.98
mod6: my apologies
mod6: thanks!
mod6: asciilifeform: yeah, i dunno what i screwed up with that integration patch of mine, but yeah, your vpatch fix pressed and compiled fine.
mod6: yah, will try here now.
mod6: even after a clean.
mod6: yeah, i dunno, i got the same problem again just now.
mod6: <+asciilifeform> did you make it directly from my 2 patches (old + new) ? << no didn't even try that yet. just went straight into integration of both into one. kinda got side tracked with the SoBA and then watched some xfiles. heheh.
mod6: gotta get it to link correctly tho.
mod6: mine? should have. is basically the same as yours just instead with 'extern int VERSION;'
mod6: thanks for taking a look at that. did you see my replacement patch then?
mod6: <+asciilifeform> IT BUILDS FINE HERE << huh, maybe i didn't clean?? i'll try again.
mod6: i just tried to avoid extra clutter in there.
mod6: where that part is above the section for [V]
mod6: makefiles, as they were submitted to the Mailing List [R.06]
mod6: NOTE: With the publication of the latest version of V [v99996] [R.05] these
mod6: oh, it does, sometimes if it's been referenced before in the document, i don't re-reference it.
mod6: mircea_popescu: that part is just in reference to V's release in R.05, not the high/low S patch which is R.09
mod6 headdrop
mod6: oh f. yah you did. dangit.
mod6: "Hier lies mod6, couldn't spell."
mod6: spelling error. christ on a pony.
mod6: ok yeah, there is a ref in there. ^
mod6: mod6's vpatch, `mod6_der_high_low_s.vpatch' [R.09]
mod6: i don't follow.
mod6: oh hey, did i screw that up?
mod6: sometimes when i'm quoteing someone, as opposed to a thing, i'll use `` '' instead.
mod6: http://therealbitcoin.org/ml/btc-dev/2016-January/000203.html
mod6: it does
mod6: all reachable leaves
mod6: meanwhile, im gonna work on getting this SoBA completed. :]
mod6: asciilifeform: <+mod6> so... i've integrated asciilifeform's fix into a new patch that will replace the old one: http://dpaste.com/2KCXN8A.txt << <+mod6> ahh, and then there is this now -- when compiling with alf's fix incorporated: <+mod6> http://dpaste.com/1AVK5ZP.txt << any thoughts on how to fix0r this?
mod6: well, i missed a few, need to clean those up :P
mod6: some of you out there who are following along will be like, "yeah, what about line 426, or 484 then!! eh!?"
mod6: np
mod6: ok.
mod6: yup yup, i put a 0x0a in there just to preseve 80 cols. but perl deoesn't care nor does it add a '\n' to the command string
mod6: notice how there is a space after '=long '
mod6: <+ben_vulpes> so the '.' is both a line-break escape and string concatenation? << its not a line break. its just a string concatenation.
mod6: and execute $import and set the result (output) of the command to $res
mod6: my $res = `$import`;
mod6: then in the next line i do this:
mod6: "command part A" . "command part B" and set that equal to $import
mod6: ok so whats going on there is that to preserve 80 cols, i create a command spanning two lines
mod6: these right ^
mod6: "--import $wdir/$pubkey 2> /dev/null";
mod6: my $import = "gpg --homedir $tdir --logger-fd 1 --keyid-format=long " .
mod6: one sec.
mod6: im retard
mod6: oh oh
mod6: what version are you looking at? perhaps my 64 & 65 are different?