Matches for patch, 1691 total results Sorted by newest | relevance
Fri Dec 18 23:47:10 UTC 2015 <ascii_field> https://bitnodes.21.co/nodes/?q=/therealbitcoin.org:0.9.99.99 << experimental programmable-versionstring patch is in test, and seen even here
Sun Dec 06 05:15:13 UTC 2015 <pete_dushenski> youth, to the extent that they have no patch of anything to call their own, are inclined to jump aboard any train promising any sort of future
Sun Dec 06 05:14:47 UTC 2015 <pete_dushenski> as well as "boomers" very strong desire to maintain, if not grow, the little patch of earth they've thus far claimed for themselves
Tue Dec 01 05:34:27 UTC 2015 <ben_vulpes> "no listen, we're super inclusive. get yourself a gpg key, get in the wot, read the logs, submit a patch, and we'll talk about it."
Sat Nov 28 21:24:05 UTC 2015 <mod6> Not a lot really remains left for v054. I'm in the process of getting all of the 3rd party deps, listed and then will sign and find a place for them on the website. Then I need to update my build script so it pulls and verifies all of that stuff from our own host. Beyond that, I just need to publish the v054-RELEASE patch I've been sitting on. Then Mr. Vulpes & I will need to sign all the vpatches and post 'em to the mailing list.
Sat Nov 28 16:41:39 UTC 2015 <ascii_field> i had the motherfucking 'play with barbarians' patch
Sat Nov 28 00:11:20 UTC 2015 <jurov> the patch adds -l dl to LIBS
Fri Nov 27 23:24:30 UTC 2015 <jurov> the jettison patch had it the other way
Fri Nov 27 23:23:56 UTC 2015 <ascii_field> jurov, phf: i recommend getting that patch of mine which lets you request EXACT bytes of heap used total at ANY TIME
Fri Nov 27 23:07:37 UTC 2015 <phf> jurov: the goal is to get bitcoind working with pogo's limited memory. the problem is that a running bitcoind grows in memory use as a result of normal operations. we know that some processes claim a lot of memory by design, like mempool, so first step is to get a reliable way of cleaning out mempool. ascii wrote that patch, but discovered that in practice zapmempool doesn't reduce memory use.
Fri Nov 27 23:02:04 UTC 2015 <assbot> Logged on 19-08-2015 14:32:04; asciilifeform: thestringpuller: this patch does not work as described, on account of boost idiocy (removal of items from the hash does not invoke their destructures! believe)
Fri Nov 27 21:58:56 UTC 2015 <phf> jurov: the overal goal though is to flush the mempool, but simply measuring the memory between zapmempool shows that the patch specifically doesn't do it. there's either additional source of leak, or there's a leak in mempool, or, and that's the most likely case, the patch in question doesn't touch al lthe places where mempool has data
Fri Nov 27 21:17:41 UTC 2015 <assbot> Logged on 19-08-2015 14:32:04; asciilifeform: thestringpuller: this patch does not work as described, on account of boost idiocy (removal of items from the hash does not invoke their destructures! believe)
Thu Nov 19 20:30:07 UTC 2015 <phf> i think maybe it's worthwhile to patch the logger so it doesn't report until the client actually does a read/write. if you do a port scan on yourself, will have same effect
Sat Nov 14 23:37:51 UTC 2015 <asciilifeform> there is only one way to reliably broadcast 1) when a particular patch came to exist 2) what the present state of the art may be.
Tue Nov 10 05:28:50 UTC 2015 <assbot> LKML: Linus Torvalds: Re: [PATCH] kdesu broken ... ( http://bit.ly/20IGXcT )
Tue Nov 10 05:28:50 UTC 2015 <assbot> LKML: Alan Cox: Re: [PATCH] kdesu broken ... ( http://bit.ly/20IGXcV )
Fri Nov 06 23:13:29 UTC 2015 <mod6> <+shinohai> mod6: have you had any sucess with bsd yet ? << yeah, OpenBSD, achieved a full sync a few months back. had to patch it by hand.
Fri Nov 06 01:14:12 UTC 2015 <jurov> no patch needed since 0.8
Fri Nov 06 01:13:47 UTC 2015 <jurov> ascii_field: electrum-server depends on bitcoin having "txindex" which 0.5.4 not sure if has, 0.7 had and the el. patch was not heavy