home | log | search | bash | stats | wiki


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

Wed Aug 05 14:33:08 UTC 2015  <asciilifeform>   thinking of a modified unix-patch util that stuffs sha512 into comment preceding each file diff

Wed Aug 05 14:26:47 UTC 2015  <asciilifeform>   mircea_popescu: i once thought about placing antecedent hashes in patch headers

Wed Aug 05 14:25:37 UTC 2015  <punkman>   with some metadata in diff files, we could have a script that creates a branched git repo entirely out of signed patch files

Wed Aug 05 04:53:56 UTC 2015  <decimation>   thus, you need the whole repo state per patch

Wed Aug 05 04:53:37 UTC 2015  <decimation>   which you can't get unless you have the whole repo stepped forward to the state of ap articular patch

Wed Aug 05 04:53:23 UTC 2015  <decimation>   asciilifeform: for one thing, you would need to see the patch in context

Wed Aug 05 04:50:11 UTC 2015  <decimation>   for each patch

Wed Aug 05 04:50:10 UTC 2015  <trinque>   dev is its own concern which might have other processes; you could say that a particular feature branch eventually gets flattened down into a release patch

Wed Aug 05 04:49:58 UTC 2015  <decimation>   it would be nice to have a button to click: download the 'original tree' plus patches to get to this patch

Wed Aug 05 04:36:48 UTC 2015  <asciilifeform>   see the text of the patch.

Wed Aug 05 04:36:08 UTC 2015  <decimation>   asciilifeform: are the maps in question contained in your 'mempool zap patch'?

Wed Aug 05 04:30:28 UTC 2015  <asciilifeform>   ;;later tell ben_vulpes i have nothing against 'git', 'mercurial', etc., and even sometimes use these in civilian life, there is even somewhere ~horror~ a 'github' page with my name and some old crud, yes. but the ~canonical walk from pedigreed 0.5.3 to therealbitcoin~ has to be in .patch form!

Wed Aug 05 04:22:49 UTC 2015  <asciilifeform>   btw the db patch is not marked with antecedents because it has none (since last release)

Wed Aug 05 04:13:41 UTC 2015  <trinque>   the patch signing is great, but it's not a process by itself

Wed Aug 05 04:11:21 UTC 2015  <ben_vulpes>   if you're up to date on the patching, submit a patch and note its antecedents.

Wed Aug 05 03:56:25 UTC 2015  <ben_vulpes>   not even a note in correction about "lol sry first patch doesn't work"

Wed Aug 05 03:55:32 UTC 2015  <ben_vulpes>   so ofc i /try/ first patch

Wed Aug 05 03:55:24 UTC 2015  <ben_vulpes>   second patch contained a link to mp's "dis wat i do, yo"

Wed Aug 05 03:55:08 UTC 2015  <asciilifeform>   just 'here's a patch, i'd better eat it'

Wed Aug 05 03:54:50 UTC 2015  <asciilifeform>   srsly, ben_vulpes managed to install the uncorrected patch in the minutes between it and the new one ??

« Previous Page    Next Page »