home | log | search | bash | stats | wiki


Matches for patch, 1691 total results Sorted by newest | relevance

Sun Jan 31 07:54:27 UTC 2016  <punkman>   http://log.bitcoin-assets.com/?date=30-01-2016#1390093 would provide hands-off testing to see whether your new patch compiles to different archs, with different libc, etc. think jenkins

Sun Jan 31 04:55:07 UTC 2016  <mod6>   and... its maybe slightly different since the first patch was inclued in the first release.

Sun Jan 31 04:51:02 UTC 2016  <mod6>   and i'll also have to "re-grind" my high/low S patch

Sun Jan 31 04:50:30 UTC 2016  <mod6>   <+pete_dushenski> ver 99999 is fine by me << yeah, this is fine. but the fact that it doesn't do what it should do isn't. i'll pull the patch tomorrow.

Sun Jan 31 04:49:35 UTC 2016  <asciilifeform>   likewise it appears that the shiva patch has an issue, you end up having to LC_ALL="C" ./bitcoind -shivainit=./shiva/init.scm -shiva getinfo

Sun Jan 31 04:47:39 UTC 2016  <asciilifeform>   will be happy to produce an antimatter patch for it if this is needed.

Sun Jan 31 04:47:12 UTC 2016  <asciilifeform>   mod6: i officially pronounce the verstring patch to be buggy and unfit for inclusion in its present state

Sun Jan 31 04:36:24 UTC 2016  <phf>   "patch" is surprisingly trivial once you get past unified diff format parsing, http://paste.lisp.org/display/306234

Sun Jan 31 01:54:39 UTC 2016  <ascii_rear>   but, 1) there is a skull on the patch for a reason 2) there is not actually an alternative to tinyscheme.

Sat Jan 30 23:34:17 UTC 2016  <phf>   i pressed it programmatically, without "patch" utility, before leaving home, so didnt have time to test it

Sat Jan 30 18:34:40 UTC 2016  <phf>   ben_vulpes: so actually inside the patch hunks are grouped by files, what i was referring to as hunks are actually per file hunk groups. so in other word the graph is already edge-per-file. i added the labels but it looks dodgy http://glyf.org/tmp/labels1.png http://glyf.org/tmp/labels2.png

Sat Jan 30 06:39:47 UTC 2016  <ben_vulpes>   first: node.js. second: "naw, vpatches are for faggots". third: 2.5kloc patch degendering reference implementation log statements.

Fri Jan 29 23:40:39 UTC 2016  <phf>   and the one ascii requested, transition graph for when there's only one hunk per patch file http://glyf.org/tmp/trb-transition-hunks-asplode.png (i filtered out all the genesis files that don't have further transitions)

Fri Jan 29 21:49:49 UTC 2016  <shinohai>   I know the patch applied, because bitcoind -? shows it as an option

Fri Jan 29 21:29:30 UTC 2016  <assbot>   Logged on 21-01-2016 15:48:48; asciilifeform: mod6, shinohai: the version string patch works. BUT you will always see the default version in the boot log!! because said printf ~precedes~ the setting of the custom string. this may explain shinohai's confusion.

Fri Jan 29 21:16:26 UTC 2016  <pete_dushenski>   mod6: i have a question about the version string patch... i seem to have applied it correctly but i'm still seeing version "50400" even when trying the '-setvernum' command so i'm not sure what i'm doing wrong. this is a new instance that's in the process of syncing, not 'tevye', which properly shows '99999'. i used the original 99997k script and applied 'version-strings' and 'hearnificarum' manually and both are now

Fri Jan 29 20:38:47 UTC 2016  <mod6>   # Required Public Keys to add to your PGP Keyring. These are used to verify V, rotor, buildroot, and trinque's patch:

Fri Jan 29 20:38:25 UTC 2016  <mod6>   # Required Public Keys to add to your PGP Keyring. This are used to verify V, rotor, buildroot, and trinque's patch:

Fri Jan 29 20:33:23 UTC 2016  <phf>   having multiple hunks in a patch modify several files at the same time creates a harder transition constraint then simple antecedent/descendent pairing, so i'm thinking it's probably safe to construct a graph in terms of transitions rather then purely a/d. the end result should be the same

Fri Jan 29 20:32:18 UTC 2016  <phf>   mircea_popescu: anyway, i was speaking of how things are right now in v.py/v.pl. a hunk touches a file, hunks are grouped thematically (i.e. by a single unit of meaning) in a patch. a pairing of antecedent/descendent creates a graph and in combination with topo logical sort produces a press order

« Previous Page    Next Page »