Matches for patch, 1691 total results Sorted by newest | relevance
Tue Sep 15 19:01:47 UTC 2015 <mod6> as far as the 'experimental' patches, i agree about the 'maxint_locks' patch.... maybe there's a better word than experimental. and, anyway, this will all change soon anyhow, so not sure how urgent it is.
Tue Sep 15 19:01:39 UTC 2015 <ascii_field> mats: seller, for instance, can disclose the patch immediately after sale
Tue Sep 15 03:33:16 UTC 2015 <asciilifeform> if it is done intelligently, it is easily $2-3K PER PATCH
Tue Sep 15 03:33:03 UTC 2015 <trinque> does this require a musl patch? does this ...
Sat Sep 12 16:50:49 UTC 2015 <assbot> Logged on 12-09-2015 08:18:01; punkman: ;;later tell asciilifeform my ugly solution to patch conflicts http://dpaste.com/03TADM8
Sat Sep 12 08:18:01 UTC 2015 <punkman> ;;later tell asciilifeform my ugly solution to patch conflicts http://dpaste.com/03TADM8
Fri Sep 11 09:49:28 UTC 2015 <mircea_popescu> "this bear likes to fuck people ; you an tell it's horny by the red patch above its nose" IS a warning.
Fri Sep 11 09:18:58 UTC 2015 <punkman> on an unrelated note, I think I have a rough algorithm for dealing with V patch conflicts
Thu Sep 10 02:00:03 UTC 2015 <asciilifeform> mircea_popescu: aha it takes a destionation dir name and a patch name (called in this case 'head'). applies sequence up through and including head.
Wed Sep 09 21:44:37 UTC 2015 <mircea_popescu> "Anyone who has arrived early at a general admission event will recognize the feeling. You lay out your blanket, thus marking off a small piece of territory for yourself. The other early arrivals do the same. After a while, you start to feel as though that patch of land is yours by right.
Wed Sep 09 21:01:45 UTC 2015 <ascii_field> these would expand to actual (colourized) diffs which the patch in question concerned.
Wed Sep 09 20:57:22 UTC 2015 <ascii_field> to see what i mean, try adding a patch that depends on a rel1 terminus but is not built on by anything else.
Wed Sep 09 20:12:55 UTC 2015 <jurov> i remember we discussed when the patch went in
Tue Sep 08 09:55:34 UTC 2015 <cazalla> http://log.bitcoin-assets.com/?date=08-09-2015#1266188 <<< pretty much stand on iphone.. patch notes always "bux fixes and improvements" and that's it, no actual list
Sun Sep 06 17:18:19 UTC 2015 <asciilifeform> (that is, all 'generations' of patch family tree should occupy a level, strictly)
Sun Sep 06 17:08:59 UTC 2015 <punkman> asciilifeform: I just noticed this earlier when I looked at press, will apply every single patch up to HEAD
Sun Sep 06 17:06:37 UTC 2015 <asciilifeform> ben_vulpes: try producing a patch that forks off, e.g., rel1, and see what i mean.
Sun Sep 06 17:00:05 UTC 2015 <asciilifeform> let's say it weren't. then ' ./v.py w ' prints wot ? but this is broken. because what if 'w' is my patch dir, and i simply forgot to include the second arg.
Sun Sep 06 16:59:33 UTC 2015 <asciilifeform> but the patch dir arg is necessary !
Sun Sep 06 15:52:13 UTC 2015 <asciilifeform> ;;later tell ben_vulpes what were you trying to do ?! 'o' takes a ~tree file's hash~ as argument, and tells you ~which patch~ produced it. looks like you were giving it a patch's hash ??