Matches for patch, 1691 total results Sorted by newest | relevance
Sun Feb 21 01:42:33 UTC 2016 <mircea_popescu> it is not YOUR fucking patch.
Sun Feb 21 01:42:03 UTC 2016 <asciilifeform> mircea_popescu: say we do things precisely as you described. and tomorrow i publish a patch. now everyone who wants to test it, cannot apply it at all unless he is willing to use my tree wholesale. instead he has to MANUALLY merge it in, line by line. and then i end up back-and-forth-ing over his typos for the next month, instead of doing ANYTHING else
Sun Feb 21 01:38:22 UTC 2016 <mircea_popescu> but in any case, what i expect in practice is - a lot of cross signing, of people who know each other ; and a ready spot for corporate investment. "make me a mod6+alf patch" is a job.
Sat Feb 20 23:42:04 UTC 2016 <mircea_popescu> you don't "release" a patch.
Sat Feb 20 23:41:53 UTC 2016 <assbot> Logged on 20-02-2016 23:33:14; asciilifeform: to the point where i cannot even release a patch because wtf, against ~what~ do i patch
Sat Feb 20 23:37:35 UTC 2016 <asciilifeform> the patch set must physically come from somewhere.
Sat Feb 20 23:33:14 UTC 2016 <asciilifeform> to the point where i cannot even release a patch because wtf, against ~what~ do i patch
Sat Feb 20 23:31:05 UTC 2016 <asciilifeform> and when i said 'patch set' it means that - like it or not - you gotta get them somewhere.
Sat Feb 20 22:45:43 UTC 2016 <phf> "i, ordained computron mircea lifeform, in the year of our republic 1932, having devoted three months to the verification of checksums, with my heart pure and my press clean, sit down to transcribe vee patch ascii_limits_hack, signed by the illustrious asciilifeform, mircea_popescu, ben_vulpes and all saints."
Sat Feb 20 21:51:10 UTC 2016 <ben_vulpes> you will get a release patch and you will press to it. there is your hammer.
Sat Feb 20 21:50:33 UTC 2016 <ben_vulpes> *i* want to press specified patch sets without doing so by hand.
Sat Feb 20 21:47:42 UTC 2016 <ben_vulpes> then press to a release patch, fin.
Sat Feb 20 21:42:52 UTC 2016 <mircea_popescu> http://log.bitcoin-assets.com/?date=20-02-2016#1410922 << would we do me the favour and quote me when we agree with me like this as i have nfi what this is. also http://log.bitcoin-assets.com/?date=20-02-2016#1410930 <<< what stupid shit is this! specify THE PATCH SET ? fu! you mean specify the wot and the genesis ?
Sat Feb 20 21:42:52 UTC 2016 <assbot> Logged on 20-02-2016 20:07:06; asciilifeform: pete_dushenski: you still have to specify the patch set
Sat Feb 20 20:13:14 UTC 2016 <asciilifeform> ideally patch hopper oughta deedbot also.
Sat Feb 20 20:08:13 UTC 2016 <asciilifeform> where do i put a patch so that everybody ~immediately~ sees it ?
Sat Feb 20 20:07:06 UTC 2016 <asciilifeform> pete_dushenski: you still have to specify the patch set
Thu Feb 18 20:20:59 UTC 2016 <assbot> Logged on 18-02-2016 18:44:46; linton_s_dawson: I thought about what may improve the TMSR infrastructure and figured that the logs themselves are somewhat difficult to navigate. "Catching up" with the logs means reading through the whole conversation until you stumble upon what matters. I.e. "a new patch was proposed" or "MP uncovered the next scam in the making".
Thu Feb 18 18:44:46 UTC 2016 <linton_s_dawson> I thought about what may improve the TMSR infrastructure and figured that the logs themselves are somewhat difficult to navigate. "Catching up" with the logs means reading through the whole conversation until you stumble upon what matters. I.e. "a new patch was proposed" or "MP uncovered the next scam in the making".
Wed Feb 17 15:58:46 UTC 2016 <phf> (so to wrap up previous thread, patches will remain, until clicking any patch in that graph produces a press, ideally clicking on one of the patches from mod6 release should produce press identical to mod6's press even in the presence of conflicting patches. i'll solve this problem sometime this week)