Matches for patch, 1691 total results Sorted by newest | relevance
Fri Jan 22 04:09:29 UTC 2016 <assbot> Logged on 21-01-2016 14:40:51; mircea_popescu: that once the current version being worked upon is released, we all do a whole-source scouring of spaces, and sign the independently generated results, which will be an immediate, other patch.
Fri Jan 22 03:52:36 UTC 2016 <mircea_popescu> <mod6> after i apply his patch, there are no tabs, only spaces. << i made a tab'd one, then asciilifeform wanted a different one so i made that too. which are you looking at ?
Fri Jan 22 03:34:32 UTC 2016 <mod6> <+mod6> huh, dunno, guess i could try that. << failed to patch
Fri Jan 22 03:29:06 UTC 2016 <mod6> who knew that creating the patch would be harder than the code itself.
Fri Jan 22 03:27:23 UTC 2016 <mod6> after i apply his patch, there are no tabs, only spaces.
Fri Jan 22 03:24:10 UTC 2016 <mod6> i gotta figure out how to get this patch exactly correct. can't seem to do it.
Fri Jan 22 03:07:28 UTC 2016 <mod6> it pretty much applies the same, and if then I do a vdiff of a/bitcoin/src/key.h to b/bitcoin/src/key.h (where Mr. P.'s patch was applied in b/.../) then the diff looks the same.
Fri Jan 22 00:55:49 UTC 2016 <BingoBoingo> pete_dushenski: Much to be said for the learning value of patch by hand in addition to doing V-presses
Fri Jan 22 00:24:12 UTC 2016 <assbot> Logged on 21-01-2016 14:40:51; mircea_popescu: that once the current version being worked upon is released, we all do a whole-source scouring of spaces, and sign the independently generated results, which will be an immediate, other patch.
Thu Jan 21 15:52:30 UTC 2016 <mod6> <+asciilifeform> mod6, shinohai: the version string patch works. BUT you will always see the default version in the boot log!! << personally I haven't even tried this yet. but I think he was saying that he checked the getinfo and that hadn't updated either.
Thu Jan 21 15:48:48 UTC 2016 <asciilifeform> mod6, shinohai: the version string patch works. BUT you will always see the default version in the boot log!! because said printf ~precedes~ the setting of the custom string. this may explain shinohai's confusion.
Thu Jan 21 15:44:50 UTC 2016 <mod6> <+asciilifeform> mod6: what was this about 'snags' with the version patch ? << i'll dig it up, just a sec.
Thu Jan 21 15:44:31 UTC 2016 <asciilifeform> mod6: what was this about 'snags' with the version patch ?
Thu Jan 21 15:44:17 UTC 2016 <mod6> <+mircea_popescu> well, i do think to some degree your patch should be restated, but not in the sense of replacing it altogether << yeah, ok. i'll do some work here today / tonight, do a re-test and the hopefully get it to the ML before the week is out.
Thu Jan 21 15:42:09 UTC 2016 <mircea_popescu> well, i do think to some degree your patch should be restated, but not in the sense of replacing it altogether
Thu Jan 21 15:41:28 UTC 2016 <mod6> <+mircea_popescu> well, honestly, this wasn't intended as a release candidate, more like a commentary item << ok good deal. was kinda wondering if the forthcoming release patch should bundle this one in or not.
Thu Jan 21 15:38:29 UTC 2016 <mod6> your patch really is easier to read since leaving in the vchSig.clear() etc at the top instead of moving it to the bottom like mine had.
Thu Jan 21 14:40:51 UTC 2016 <mircea_popescu> that once the current version being worked upon is released, we all do a whole-source scouring of spaces, and sign the independently generated results, which will be an immediate, other patch.
Thu Jan 21 13:49:20 UTC 2016 <asciilifeform> mircea_popescu: 1 patch for the meat, another where just munge
Thu Jan 21 13:48:26 UTC 2016 <asciilifeform> mircea_popescu: you realize, this is likely the biggest patch so far