Matches for patch, 1691 total results Sorted by newest | relevance
Thu Nov 05 20:55:46 UTC 2015 <phf> luckily for you today only you can get a new and improved PATCH from me that will at least let you create context, since i only finished it like last night, i don't yet know if it will actually encrypt, but it might
Thu Nov 05 15:09:10 UTC 2015 <asciilifeform> http://log.bitcoin-assets.com/?date=05-11-2015#1317131 << might want to patch trb's version thing instead
Thu Nov 05 01:19:49 UTC 2015 <asciilifeform> trinque: there was a patch. iirc it didn't make it in for some trivial reason
Wed Nov 04 17:13:22 UTC 2015 <trinque> you recommend a separate proggy rather than patch to bitcoind?
Mon Nov 02 14:43:54 UTC 2015 <asciilifeform> whole thing is a trivial example of 'can operate entirely as a small patch on a bitcoind'
Sat Oct 31 16:35:53 UTC 2015 <assbot> diffutils.git - GNU diff and patch utilities ... ( http://bit.ly/1P36dGM )
Wed Oct 28 20:44:12 UTC 2015 <ascii_field> davout: this kind of braindamage has been around for some years, yes. but until now i did not know that it has reached the point where you have to patch ~the printer itself~ rather than merely the eeprom in the cartridge.
Wed Oct 28 18:42:38 UTC 2015 <assbot> Logged on 28-10-2015 16:56:05; ascii_field: funkenstein_: i recommend dpasting your patch for review before signing formally
Wed Oct 28 16:56:05 UTC 2015 <ascii_field> funkenstein_: i recommend dpasting your patch for review before signing formally
Wed Oct 28 16:55:01 UTC 2015 <mod6> vdiff.sh a b > your_patch_name.vpatch
Wed Oct 28 16:53:25 UTC 2015 <assbot> Logged on 28-10-2015 16:30:06; funkenstein_: so after a number of tests I was going to submit the fix on this patch, but after using V more often it has become clear that it is annoying to have patches made from different places in the directory
Wed Oct 28 16:47:19 UTC 2015 <funkenstein_> of course V still can be used in either case to apply any patch you like made from anywhere, just a minor annoyance
Wed Oct 28 16:30:06 UTC 2015 <funkenstein_> so after a number of tests I was going to submit the fix on this patch, but after using V more often it has become clear that it is annoying to have patches made from different places in the directory
Mon Oct 26 17:08:11 UTC 2015 <funkenstein_> in this instance, i assume a properly measured replacement of the thing is preferred to an additional patch to fix
Mon Oct 26 11:09:56 UTC 2015 <funkenstein_> so if anybody wants a signed antipatch for my broken patch, let me know. otherwise, I assume the thing can be simply dropped.
Sun Oct 25 20:44:33 UTC 2015 <mod6> yeah. that patch won't be added into the mirror. now if someone wants to try out his patch locally, they'll have to pull his vpatch, and add his key to the wot manually and then see what happens if they want to press out a branch that includes that vpatch.
Sun Oct 25 20:43:30 UTC 2015 <asciilifeform> e.g. funkenstein's latest patch will need an antipatch
Sun Oct 25 18:33:10 UTC 2015 <assbot> LKML: Matthew Garrett: [PATCH 04/12] x86: Lock down IO port access when trusted_kernel is true ... ( http://bit.ly/1GAWd4H )
Sat Oct 24 17:54:27 UTC 2015 <asciilifeform> i had one when i was in school, and it worked great. but today - nope. because go and try to install freebsd 4.7 - where do you get the packages? gonna patch by hand ?
Fri Oct 23 19:15:31 UTC 2015 <ascii_field> see his patch, http://therealbitcoin.org/ml/btc-dev/2015-October/000172.html