home | log | search | bash | stats | wiki


Matches for patch, 1691 total results Sorted by newest | relevance

Wed Aug 05 22:35:26 UTC 2015  <mod6>   well and probably error prone if he/she has to cut the upper text out just to get down to "bare" patch to re-clearsign and submit to deedbot... could miss line, something bad.

Wed Aug 05 22:34:10 UTC 2015  <ascii_field>   esp since >1 person can sign a patch

Wed Aug 05 22:26:54 UTC 2015  <ascii_field>   throw message prior to the first 'diff ....' in the ,patch

Wed Aug 05 22:25:27 UTC 2015  <mod6>   ok so another question i have about the deedbot way.. would be: if we submit a patch to deedbot, how do we tie a message to that same submission? say we wanna be like "Hey, this thing is neat!" Will it need to reference anothe deedbot submission or does the patch have to come after our statment in the clearsigned message?

Wed Aug 05 22:17:16 UTC 2015  <mod6>   *patch file.

Wed Aug 05 22:12:40 UTC 2015  <mod6>   <+jurov> mod6 decrypt on *clearsigned* file << this indeed works. created file A.txt. copied A.txt to B.txt and subtracted some lines. created a unified diff of both. clearsigned the diff -- which is mutilated for escaped hyphens. upon `gpg --decrypt` of the clearsigned output patch file, i get the same hash as the pre-clearsigned hash file.

Wed Aug 05 22:10:17 UTC 2015  <mircea_popescu>   pruning the tree of all ulteriors that depend on an unclicked patch

Wed Aug 05 22:06:35 UTC 2015  <mircea_popescu>   trinque and with a bonus "click here for this patch" and "click here for this patch + all its antecedents" spew.

Wed Aug 05 21:55:34 UTC 2015  <mod6>   i guess for me thats the one big thing, we can't have any mutilation of the patch files. or we'll just find ourselves banging our heads all the time.

Wed Aug 05 21:53:28 UTC 2015  <jurov>   well, if gpg can't undo it and it causes the patch to fail...then it fails.

Wed Aug 05 21:49:14 UTC 2015  <assbot>   Logged on 05-08-2015 18:55:16; mod6: now, it might be that I'm not exactly understanding what the proceedure for submitting to deed bot would be. but if clearsigned .patch files, that can not work.

Wed Aug 05 21:33:33 UTC 2015  <assbot>   Logged on 05-08-2015 18:55:16; mod6: now, it might be that I'm not exactly understanding what the proceedure for submitting to deed bot would be. but if clearsigned .patch files, that can not work.

Wed Aug 05 19:29:24 UTC 2015  <jurov>   but it's universally usable to (1) determine what version patch applies to (2) allows to remove files without listing whole contents

Wed Aug 05 19:29:21 UTC 2015  <ascii_field>   that requires either modified 'patch' util, or wrapped in perl etc

Wed Aug 05 19:29:09 UTC 2015  <mod6>   it does now, or it will because we must now reinvent diff/patch ?

Wed Aug 05 19:28:32 UTC 2015  <jurov>   no, must roll ou our won diff/patch

Wed Aug 05 19:27:41 UTC 2015  <mod6>   ok and that sha512 hash is of the file /before/ the changes were made resulting in the patch?

Wed Aug 05 19:25:51 UTC 2015  <jurov>   mod6 you have seen alf's patch with embedded sha512 example?

Wed Aug 05 19:23:40 UTC 2015  <ascii_field>   while preserving the simultaneously total and minimal representation of .patch

Wed Aug 05 19:14:13 UTC 2015  <jurov>   and metadata what the patch applies on

« Previous Page    Next Page »