2100+ entries in 0.271s
adlai: well, the missing
patch is resolved; but the missing cpio - is a bug.
ben_vulpes: this gulf between computers as toys and computers as devices to be used by people who can
patch, understand what the machine is doing stretches wider every day.
ben_vulpes: phf: why doesn't funkenstein's privkey tool
patch show up on the
patch graph?
mod6: phf: you may want to add the 'makefiles.vpatch' to your
patch thingy.
mod6: One of the last changes I made was to rid the 'shit' directory, and just use one directory; 'deps'. At which point the rotor & rotor
patch were deedified.
phf: so i use it to put a
patch description, but if the section has ^L\n( or ^L\n; then i just execute everything between ^L and diff ... after the
patch has been applied
scriba: Logged on 2016-09-18: [18:14:14] <asciilifeform> i actually considered all of this in '07 but rejected because 'idiots will
patch it to do jit and bring back all of the evils'
phf: BingoBoingo: are you running the openbsd
patch?
mod6: the two .sh scripts you have in there can be integrated into the makefiles directly i think. however, we'll still need the openssl-004-musl-termios.
patch and rotor_buildroot_dot_config
deedbot: trinque rated phf 2 at 2016/02/09 09:32:36 << provided example CL code for next deedbot, made excellent v-
patch viewer, intelligent fellow
trinque: right. in this case I challenge anyone to find a need for a second
patch on those modules themselves, rather than creating a genesis vpatch for their own module which talks to the db in postgres.
☟︎ phf: diana_coman: i think i didn't say enough on the subject. the core of what i did in order to get it to build on mac os x is fix autoconf scripts, if i revisit mac os x build in a couple of weeks, i'll try and provide a portable
patch phf: i need to
patch site icon on that host, it still T
mod6: so if i see the "dump priv key"
patch out there on btcbase or found somewhere else (it's not included in the patches in thebitcoin.foundation's site), then i'd pull that vpatch down, regrind it myself, and place it into patches where I can apply it myself as a "WILD"
patch.
mod6: <+phf> asciilifeform: i did, he said something about "this being work in progress and don't want to commit" or somesuch << i could regrind them, yeah. ideally, each who want to use these unexamined items should do so on their own accord, placing them in their patches directory as a "WILD"
patch. Until the day when the foundation moves forward and folds them in after examination and testing.
☟︎ mircea_popescu: there's places for flexibility ; but this isn't one. i dun even wanna think about "creative" solutions such as "retrocreate a genesis". just god damned it already, take the code, sign it, and then
patch on the basis of that.
mircea_popescu: sure ; and there's multiple people and not everyone's yet mentally comfortable with the whole thing which is why people do the "
patch replacing
patch" thing.
Framedragger: only one last step was left!!! just need to..
patch.. it's legit guyz
mod6: <+asciilifeform> ^ the corrected
patch. << I've got these changes in now.
mod6: <+asciilifeform> anyway the
patch ^ shown above is the ticket. << recompiling for gpg2
mats: my understanding of his point is that proof-of-solvency is a monkey
patch that attempts to paper over defects in human relations with technical solutions
shinohai: ben_vulpes: i didn't have to do anything to get it all to work besides diff and apply phf 's
patch and directions
a111: Logged on 2016-08-14 05:12 ben_vulpes: phf, shinohai, trinque, asciilifeform, mircea_popescu: i elected to nuke the "stale comments" thing, i'd be much obliged if any of y'all have a
patch for that. in exchange i've got a
patch on wp-comments.php for the suffix trick, not that it's hard or anything
ben_vulpes: phf, shinohai, trinque, asciilifeform, mircea_popescu: i elected to nuke the "stale comments" thing, i'd be much obliged if any of y'all have a
patch for that. in exchange i've got a
patch on wp-comments.php for the suffix trick, not that it's hard or anything
☟︎ ben_vulpes: anyways, i am *still* looking for the comment-fixin
patch trinque: asciilifeform: isn't, but I can package it up later. I hand-applied phf's
patch to a custom skin mangled from the "classic" skin.
trinque: shinohai: ah the
patch diddles wp-content too; got it now
shinohai: yeah I unpacked it all the applied
patch, built database and was good to go
trinque: shinohai: what am I supposed to do, unpack then apply that
patch?
trinque: shinohai: ben_vulpes gave me the wad o' wp-mp you gave him. am I supposed to apply this
patch, or is it already applied? it broke when applying
phf: ben_vulpes: i have a patchset, that takes wp from stock 2.7 to mircea_popescu's version, and then adds a few cleanups that i did. once i get through all the other shit i'm working on, i'll release it. the stock->mp
patch is useful if you want to do further work on the codebase and have some idea where mp's custom patches begin and end
hanbot: i had the same problem with V99994, ftr i suspect it's a user permissions issue as when i try to manually check that sig against the vpatch gpg complains it can't open the file (and that particular
patch was just alphabetically first, ergo not special)
mircea_popescu: i have, and saw enough burns. that
patch of skin was welted by application of a cane, not fucking "laser"
mircea_popescu: it just doesn't actually speak to the foregoing. i suppose the correct rsa implementation comes with a kernel
patch.
mircea_popescu: course iirc phf released a
patch version including basic theme and pre-tweaked most knobs.
mircea_popescu: and yes, the derp was broadly correct, itwas "in that general direction" and so forth. but omfg
patch of salt!
mircea_popescu: either lift it from his
patch or else put it in the theme comments under comment_post_ID
phf: shinohai: if you unpack mp's tarball, unpack wp-content into it, apply the
patch, you should end up with a working instance
mircea_popescu: neway, it's like sewing on old, sunbaked rag. the more you
patch, the more it breaks.
phf: to some extent it's aligned with v model, the only thing that matters is the text of
patch, you read it, and decide on whether you want to sign it or not
a111: Logged on 2016-06-29 22:54 pete_dushenski: $rate funkenstein_ 2 trb privkey
patch guy
deedbot: pete_dushenski rated funkenstein_ 2 << trb privkey
patch guy
ben_vulpes: > latest
patch to source tree from january 2006
a111: Logged on 2016-06-20 04:23 phf: which is handy if you're using something else to produce the
patch, or if you need to use a non-trivial diff command. for example i sometimes need to exclude files from diffing, so a command might look like diff -x foo -x bar -x qux -ruN a b | grep -v '^Binary files ' | vdiff > foo.vpatch
phf: which is handy if you're using something else to produce the
patch, or if you need to use a non-trivial diff command. for example i sometimes need to exclude files from diffing, so a command might look like diff -x foo -x bar -x qux -ruN a b | grep -v '^Binary files ' | vdiff > foo.vpatch
☟︎☟︎☟︎ phf: and the other one, and main reason for posting, is that you can use it in a pipe. like diff -uNr a b | vdiff to vdiffy-y any regular
patch phf: for interested parties, i have a modified version of vdiff.
http://paste.lisp.org/display/318813 (this one is mac specific, so if your shasum is different command you need to
patch that, otherwise it should be portable)
phf: i think that a lot of these conversations come to a standstill because they deal with infinities, rather the shaping into a reasonable concrete. it seems proper that slapping new code onto bitcoin should come in a form of wot signed balls of mud, that don't particularly care about preserving all information and pedigrees and such. "i wrote this new math function and it uses this mp code that i lifted elsewhere but shaped enough that only relevant bits remain and for all practical purposes all you see in this
patch is all that matters"
phf: asciilifeform: i understand that but you're missing what i'm saying. you yourself said that you're not particularly trusting tinyscheme. it has overflow bugs, it has all kinds of issues, and keeping its apartness insulates ~you~ from a certain amount of responsibility. it's no longer serving a purpose as part of a bigger trb
patch, now it's this third party "pedigree" thing, that we can sort of rely on, but nobody's responsible for etc.
mircea_popescu: why'd someone make a new 0 diff
patch instead of signing yours ?
mod6: so what would your implementation look like here? a
patch to a current leaf of the trb patches that inflates say t/t.pl from 'false' on the end of the trb 'light-code' ?
mod6: don't add nsa's key to your wot, and you wont see that
patch right?
mircea_popescu: there is no such thing as "cannonical", but there is a "total
patch universe".
mircea_popescu: "mpapis commented Dec 22, 2014 it is standard and harmless thing, but ruby could allow filtering out this flags, this could be done as part of the filtration process that already happens in preprocessing in miniruby - but I do not think it would be considered as a ticket without pull request /
patch to address this problem."
Framedragger: mircea_popescu: with timeout per host set to 5sec (default) and unaltered parallel scanning setting (ssh-keyscan does parallel stuff pretty well but it may not be best for scanning huge numbers of hosts; case in point: default version for ubuntu 14.04 terminates if a single remote host closes conn prematurely - needed to
patch this..), it took ~65 minutes (i've started logging timestamps afterwards but this is prob quite accurate). this
mircea_popescu: although some pretty major cataclysm is needed to invalidate a genesis. you can just
patch it into correctness downstream neh ?
phf: the second meaning is, and that one comes up since we have multiple files to a
patch, in order to press x i need both y and z.