28 entries in 0.34s
mod6:
bitcoin-asciilifeform.4-goodbye-win32.vpatch, asciilifeform_dnsseed_snipsnip.vpatchasciilifeform_zap_showmyip_crud.vpatchgenesis.vpatch
mod6: There is an edge betwee"
bitcoin-asciilifeform.4-goodbye-win32.vpatch" and "asciilifeform_dns_thermonyukyoolar_kleansing.vpatch" which causes my V to think that "asciilifeform_dns_thermonyukyoolar_kleansing.vpatch" still belongs in the flow.
mod6: after a closer look on my side, you got that specific error because you were missing: '
bitcoin-asciilifeform.1.vpatch'
mod6: ../../../../patches/
bitcoin-asciilifeform.4-goodbye-win32.vpatch:+++ b/bitcoin/src/headers.h b86114b5b74d2b9e737798f78804439c5cdd0ae42440615c57fc85cb0ac7d8b8a454d2ef44048db6af0ca00a938178173eece431b273462dbc299c1501b86600
phf: i'm using graphviz, v.lisp produces a file of 'digraph G {"
bitcoin-asciilifeform.4-goodbye-win32" -> "asciilifeform-kills-integer-retardation"; ...' format, everything else handled by graphviz
mod6: any way the real sig name is currently "
bitcoin-asciilifeform.1.vpatch.mod6.sig" not <+jurov> only the question what is the '1' in
bitcoin-asciilifeform.1.mod6.vpatch.sig doing there
jurov: only the question what is the '1' in
bitcoin-asciilifeform.1.mod6.vpatch.sig doing there
jurov:
bitcoin-asciilifeform.1.mod6.vpatch.sig
mod6: yeah, i don't grasp that part fully yet. but it does make sense from genesis up through patches/
bitcoin-asciilifeform.4-goodbye-win32.vpatch
decimation: ~/bitcoin-v009/build/chicken/
bitcoin-asciilifeform.1.patch.sig
mod6: hmm, still, should be ok. i just re-ran on my side and got: >> Signature verified for
bitcoin-asciilifeform.1.patch.sig
mod6: - --verify chicken/
bitcoin-asciilifeform.1.patch.sig