log☇︎
8671 entries in 0.846s
mod6: phf: was this the page you were trying to follow?
jurov: phf, if you can make better patchlist, are you willing to contribute your script?
mod6: so phf brings to light a good point, reading through the email list, especially if you haven't read the b-a logs from oct-14 on is probably more than a bit hard to follow. ascii_field brings up a good point about having a 'family tree'
jurov: phf why you're not in such and such position?
assbot: Logged on 03-07-2015 19:44:53; phf: mod6: well, lets say you have something like mutt open with the current email. it's pretty easy to write a script that takes current email and feeds it to an external script, that splits out patch, verifies it with the provided sig, and then applies it to the codebase (or pushes it into some queue of patches as a case may be). i.e. you read the email, push "p" to do everything for you, and then move on to the n
mod6: phf: yeah, im not sure what you're asking for
mod6: phf: there are specific reasons why the attachments are split into separate files.
mod6: <+phf> mod6: no no each email. i thought that was the whole point of ascii's approach, i.e. linux kernel style "read email, think, apply the patch" << im not sure what their process is.
mod6: <+phf> the process was needlessly complicated since my mail client lets me do a bunch of those steps (patching, gpg verifying, etc) with a single key, so if i had an mbox, i could just import it, and then use a more familiar interface << so, what I've done in the past was; create a perl script that pulls down and verifies all the patches and applies them to a common baseline.
mod6: phf: anyway, what exactly is it that you're trying to achieve?
trinque: phf: you could crawl that patches page maybe
ascii_field: phf: post it to therealbitcoin.org ml!
ascii_field: phf: neato!
assbot: Logged on 02-07-2015 21:36:09; phf: maze of twisty little passages, all alike
mircea_popescu: phf you know minigame's looking for someone who can compile of apple so ben_vulpes can play.
assbot: Logged on 02-07-2015 00:17:31; phf: all patches except reward overflow, cuminer snip and igprof, up to eatblock. mac os 10.8, built dynamically with llvm's c and cmake. synced about 5 days ago
asciilifeform: phf: what kind of node was it ?
asciilifeform: phf: by far the simplest possible way is to simply walk the binary
asciilifeform: phf: why these were absent from the original bitcoin is still an enigma to me
asciilifeform: phf: it is difficult to rule anything out at this point
asciilifeform: phf: http://btc.yt/lxr/satoshi/source/src/util.cpp#0771 << zap it
decimation: phf: I made a patch to note from which node each block comes
asciilifeform: phf: somewhere we have an anti-debug.log-rollover patch
asciilifeform: phf: if you generated this with a custom patch for the beast itself, please share this
decimation: phf: neat
asciilifeform: phf: very interesting, and probably deserves to be posted to therealbitcoin mailinglist.
assbot: Successfully added a rating of 1 for phf with note: New blood
mircea_popescu: !v assbot:mircea_popescu.rate.phf.1:a15501b9b874c832d39da21bd66e77d5c726136d1695025a7edffba5998423ff
mircea_popescu: !rate phf 1 New blood
assbot: You have not rated phf.
mircea_popescu: !rated phf
mircea_popescu: phf do you intend to publish results of your run anywhere ?
asciilifeform: phf: both patches are presently considered 'experimental' and not yet ratified by therealbitcoin.
asciilifeform: phf: in the sense that they are uselessly occupying the pipe while they're moving - they do
asciilifeform: phf: out of curiosity, what was the logic behind this hypothesis ?
assbot: You rated user phf on 16-Apr-2014, with a rating of 1, and supplied these additional notes: lisper..
ben_vulpes: !rated phf
ben_vulpes: phf: is this on os x?
ben_vulpes: hi phf!
mircea_popescu: phf am i reading what you're saying correctly , "thermonuked more efficient network utilization" ?
asciilifeform: phf: so it works precisely as one might expect.
asciilifeform: phf: read the src. bitcoind never 'requests bastard block', it requests 'next blocks' and ends up with a great many that aren't the precise next block we want
BingoBoingo: phf: It doesn't look wrong
BingoBoingo: !up phf
BingoBoingo: !up phf
assbot: Successfully updated the rating for phf from 2 to 1 with note: lisper.
ben_vulpes: !v assbot:ben_vulpes.rate.phf.1:fb393218870b21a4a538f2373afcb710a6c76d81e2dd4c73fe2df98ada1a357c
ben_vulpes: !rate phf 1 lisper.
BingoBoingo: !up phf
benkay: o wow, phf. that's...news to me.
benkay: kashchenit, phf?
mircea_popescu: phf hey pretty good
gribble: Request successful for user phf, hostmask phf!~phf@unaffiliated/phf. Get your encrypted OTP from http://bitcoin-otc.com/otps/5356DE4752432A9E
phf: ;;eauth phf
phf: eauth phf
benkay: phf wrote that elisp
assbot: Voicing phf without time-limit.
benkay: !up phf
gribble: Nick 'phf', with hostmask 'phf!~phf@unaffiliated/phf', is identified as user 'phf', with GPG key id 5356DE4752432A9E, key fingerprint BDDE12104FE81BE7F83B698F5356DE4752432A9E, and bitcoin address 1N3iZVTNu4kco858zTpHUkfpzAWj6Uma7S
benkay: ;;ident phf
benkay: oh phf you can !up yourself in pm now
gribble: Rating entry successful. Your rating of 2 for user phf has been recorded.
benkay: ;;rate phf 2 lisper
gribble: Currently authenticated from hostmask phf!~phf@unaffiliated/phf. Trust relationship from user benkay to user phf: Level 1: 0, Level 2: 0 via 0 connections. Graph: http://b-otc.com/stg?source=benkay&dest=phf | WoT data: http://b-otc.com/vrd?nick=phf | Rated since: Thu Jan 2 22:27:02 2014
benkay: ;;gettrust phf
gribble: Currently authenticated from hostmask phf!~phf@unaffiliated/phf. Trust relationship from user benkay to user phf: Level 1: 0, Level 2: 0 via 0 connections. Graph: http://b-otc.com/stg?source=benkay&dest=phf | WoT data: http://b-otc.com/vrd?nick=phf | Rated since: Thu Jan 2 22:27:02 2014
benkay: ;;gettrust phf
mircea_popescu: phf` lmao that's pretty kickass a name
mircea_popescu: phf ty :)
benkay: o hai phf
thestringpuller: Bugpowder_: are phf