Matches for patch, 1691 total results Sorted by newest | relevance
Mon Dec 21 22:30:28 UTC 2015 <mircea_popescu> why's it not in teh patch tree ;/
Mon Dec 21 22:17:09 UTC 2015 <asciilifeform> (a seal, recall, is a signature of a particular patch)
Mon Dec 21 07:25:27 UTC 2015 <BingoBoingo> pete_dushenski: As penance you should fire up a trb node to test the new version string patch
Sun Dec 20 22:15:29 UTC 2015 <ben_vulpes> it's vastly more likely that someone's going to need to crap out a patch for eg openssl than replace it wholesale.
Sun Dec 20 19:22:34 UTC 2015 <asciilifeform> ;;later tell jurov http://therealbitcoin.org/ml/btc-dev/attachments/20151219/mempool_dev2_a654caa4f28ed6f78906fef28060c2f46470f067.patch << why not vpatch ?
Sun Dec 20 18:45:58 UTC 2015 <asciilifeform> the only kind of thing that is 'in own tree' is a patch that has no common ancestor with ~anything~ in the genesis tree
Sun Dec 20 18:44:45 UTC 2015 <asciilifeform> just as if i had cut out a single line of a single file, and a subsequent patch relies on that line.
Sun Dec 20 18:44:04 UTC 2015 <mod6> Scenario: Guy creates vpatch that utilizes irc.h (removed in vpatch asciilifeform_ver_no_5_4_and_irc_is_gone_and_now_must_give_ip.vpatch) must ensure that Guy's patch is on it's own tree?
Sun Dec 20 18:35:43 UTC 2015 <mod6> <+asciilifeform> it would end up as an altogether other tree in the graph << so said patch to add documentation dir would be its own root?
Sun Dec 20 18:33:49 UTC 2015 <mod6> oh, i see, so like if a patch further down the line (in time) remove a file that a specific sub tree relies upon, that those become removed?
Sun Dec 20 18:31:01 UTC 2015 <asciilifeform> (a patch that uses a deleted file can be legit so long as it is not on the tree branch that contained the deletion)
Sun Dec 20 18:24:13 UTC 2015 <asciilifeform> mod6: test it with my latest patch
Sun Dec 20 02:17:49 UTC 2015 <asciilifeform> http://log.bitcoin-assets.com/?date=20-12-2015#1348260 << this is necessary (apparently i have to explain it) because WE DON'T HAVE a known-good 'patch' util
Sun Dec 20 01:17:06 UTC 2015 <mod6> if we wait until the end, we'll save some cycles -- and mathematically the hashes wouldn't come out right if somehow the files were diddled inbetween. but I can see some merit in checking after each patch is pressed.
Sun Dec 20 00:24:37 UTC 2015 <asciilifeform> and incidentally BingoBoingo, should he make use of this patch, can easily set another
Sun Dec 20 00:23:49 UTC 2015 <asciilifeform> BingoBoingo: if the latest patch is ratified by the latter, then yes
Sun Dec 20 00:19:19 UTC 2015 <asciilifeform> this is a press of the programmable-versionstring patch and down.
Sat Dec 19 22:07:38 UTC 2015 <BingoBoingo> ben_vulpes: LibreSSL node also runs with ~1GB of ram utilized at startup after last BDB locks patch because OpenBSD malloc something or other
Sat Dec 19 21:46:17 UTC 2015 <shinohai> Also asciilifeform ty for Programmable Version Strings patch
Sat Dec 19 00:22:59 UTC 2015 <mod6> <+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 << cool!