Matches for patch, 1691 total results Sorted by newest | relevance
Thu May 07 04:45:25 UTC 2015 <mircea_popescu> "?They want everything for nothing. They wouldn?t go for five seconds without being paid. And they?ll bitch about how much they?re paid, and want more. I should do a freebie for Warner Brothers? What, is Warner Brothers out with an eye patch and a tin cup on the street? Fuck, no."
Wed May 06 23:14:50 UTC 2015 <mod6> for comparison sake, here's what the machine looked like before and just after bitcoind with this patch was executed: http://dpaste.com/094DT78.txt
Wed May 06 20:04:46 UTC 2015 <jurov> nope. had to manually patch "GaramondNo8" ttf files
Wed May 06 18:31:06 UTC 2015 <mod6> I also want to focus on the testing of your patch ascii_field. If it is to be merged, we must ensure that we do not regress.
Wed May 06 18:20:52 UTC 2015 <ascii_field> mircea_popescu: take a few min. to read the patch, if you have not. the behaviour should be logically equivalent to virginal 0.5.3 with an orphanage of zero
Wed May 06 18:16:15 UTC 2015 <mod6> ascii_field: I'm running with this patch: http://therealbitcoin.org/ml/btc-dev/attachments/20150504/asciilifeform_orphanage_thermonuke_2d219fdd1a0da960be38797566e9c0820df11ce6.patch
Wed May 06 16:46:41 UTC 2015 <assbot> Logged on 06-05-2015 14:27:11; asciilifeform: l0l, 4th google hit is my patch
Wed May 06 14:27:11 UTC 2015 <asciilifeform> l0l, 4th google hit is my patch
Wed May 06 14:19:30 UTC 2015 <davout> asciilifeform: am i correct in my understanding of the thermonuke patch that it will try to reverse-sync starting from any arbitrary block it receives?
Tue May 05 17:21:26 UTC 2015 <ascii_field> unrelated: therealbitcoin is still unbuildable for cross-arm using anything but old makefile + my (unmerged) portatronic patch
Tue May 05 12:56:03 UTC 2015 <davout> asciilifeform: really curious to see how the orphanage thermonuke patch will work in the field
Tue May 05 08:26:38 UTC 2015 <jurov> http://log.bitcoin-assets.com/?date=05-05-2015#1120242 if you have any better idea how to come up with patch ID and propagate it
Tue May 05 00:47:07 UTC 2015 <danielpbarron> http://therealbitcoin.org/mailman/listinfo/btc-dev The system will rename the patch and add unique identifier (SHA-1 hash of the contents) to the filename, both in the outgoing email and in the archives. Any additional signatures must refer to this received filename including the hash.
Tue May 05 00:35:05 UTC 2015 <mod6> yep, got that too... but check the sha256's of the dl'd patch files, see if they match the checksums that the ml inserted into the file name.
Mon May 04 23:29:53 UTC 2015 <mod6> anyway, moving on. I'll get the test in motion for asciilifeform's new patch.
Mon May 04 23:17:07 UTC 2015 <mod6> so, I have that deb6 aws env still... I used to use MRTG, but now I guess this 'RRD' thing is all the rage. I know for sure that I can test mem on a 1s interval with vmstat and capture that with `script`. I'd really like to compare the network traf of full sync with the patch, and without.
Mon May 04 23:13:24 UTC 2015 <mod6> <+ascii_field> [BTC-dev] (EXPERIMENTAL) Full Orphanage Thermonuke. << Just saw this on the train & read patch. Great work!
Mon May 04 22:20:13 UTC 2015 <ascii_field> the purpose of this patch, incidentally, was not to cure what ails us, but to make it possible to intelligently study the fragging
Mon May 04 22:16:24 UTC 2015 <ascii_field> if any part of the patch does not make immediate sense, ask now - i'm about to get into a wheeled coffin for a few hrs
Mon May 04 22:14:43 UTC 2015 <mircea_popescu> myeah reading the patch now