3400+ entries in 0.373s
mod6: <+ascii_field> [BTC-dev] (EXPERIMENTAL) Full Orphanage Thermonuke. << Just saw this on the train & read
patch. Great work!
ascii_field: the purpose of this
patch, incidentally, was not to cure what ails us, but to make it possible to intelligently study the fragging
ascii_field: if any part of the
patch does not make immediate sense, ask now - i'm about to get into a wheeled coffin for a few hrs
mircea_popescu: same "they're moving up and down on a
patch of land ; we're moving up and down on a
patch of land. what the hell's the difference!"
mod6: <+ascii_field> the
patch, note, did not remove all (there is a 'what is my ip' thing in there ) << ah, i recall. ok and this is what initiated the conversation about SHA256 addy's as opposd to dotted quads right?
mod6: we were on track at that point to try to cut a milestone. but just about that time is when we hit the tx validation problem in 168`000 ; I think your
patch just got lost in the shuffle.
ascii_field: the
patch, note, did not remove all (there is a 'what is my ip' thing in there )
mod6: is that releated to his
patch that removes the dns stuff?
mircea_popescu: friend, and the last thing I see before I black out is a
patch of yellow cheese powder inside her long tangled beard."
trinque: patches of whatever size make sense, and there's a process by which everyone else can call the
patch shit in public
mircea_popescu: i doubt the magical
patch that fixes the 1001 things will fit in 100kb for instance.
mircea_popescu: ascii_field: trinque: and if any of you produce a 100kB
patch, and i barf on general principle << there is a problem here. the code as it is is pretty long. just a simple "remove most of it" will be in the kbs.
assbot: Logged on 28-04-2015 20:04:04; Adlai: so, it's less convenient for signing a
patch relative to an upstream repo; but is exactly what you want if you just want to have a single head to put on a stake when heardbleed 2.0 gets uncovered
Adlai: ok, you sign some other dude's
patch. same diff
jurov: haven't i wrote somewhere that every productive day ends with
patch or bugreport?
trinque: seems like an ID of a
patch would obviously be some hash of it
ascii_field: trinque: and if any of you produce a 100kB
patch, and i barf on general principle and refuse to have anything more to do with project, don't say i didn't warn that vcs is harmful.
trinque: git solves this problem, and I can even email you a
patch directly out of git
trinque: doesn't make me feel smart to pluck a
patch from an email attachment
Adlai: note that darcs does NOTHING beyond '
patch -p1 < thingy'
Adlai: last thought: a signed-
patch-dev mailing list, and some trivial darcs wrapper that consumes attachments from that mailing list to frob any random repository, whether git, darks, or - for mats's's benefit - cvs. left as an exercise to the reader.
Adlai: so you either want darcs with every single
patch signed, or git
Adlai: so, it's less convenient for signing a
patch relative to an upstream repo; but is exactly what you want if you just want to have a single head to put on a stake when heardbleed 2.0 gets uncovered
☟︎ Adlai: davout: the "sign commits" feature still essentially consists of signing a merkle root of the source tree; darks lets you sign the
patch Adlai: fwiw, darcs is much more friendly to the "signed
patch" model of modification; git is better for 'signed code'; and neither are perfect
davout:
patch can't be that large to review
trinque: if we're talking about how best to
patch the raft we're riding in, sure, tape the thing and hope for the best
ascii_modem: mats: precisely same story as microshit's 'stuxnet'
patch - and hell knows how many others
pete_dushenski: doods over 40 here are working for the gov or working in the
patch nubbins`: haven't had the time to actually diff a .config before and after and turn it into a
patch BingoBoingo: mircea_popescu: Applied a
patch, cazalla's one this though.
assbot: Logged on 05-04-2015 17:22:50; nubbins`: would be nice to get some people to test this
patch when it's ready
nubbins`: would be nice to get some people to test this
patch when it's ready
☟︎ mircea_popescu: pls to make a proper
patch in full glory so people can benefit from fruits of your genius.
nubbins`: oh right, yeah, the dns-snip
patch killed that
mircea_popescu: "a bitcoind (pseudo-static, portatronic, orphanage-burner
patch with max-bastard constant value of 5 running on pogo, heathen linux.)" << i lelled.
mircea_popescu: asciilifeform it's outrageous, but hey. can you evaluate the time needeed to
patch libnss into behaving correctly ?
mircea_popescu: trinque comes down exactly to the ancient causes and purposes distinction. if people find a way to fly, nobody "deems gravity broken" or hoilds talks on how to
patch it "because this wasn't the intended result"
trinque: the problem's solved by the wot not diff and
patch trinque: running diff and
patch by hand isn't going to fix it
nubbins`: "
patch" = updating 5,000 files at once
trinque: entirely possible to use git or something else for dev,
patch process for release
nubbins`: anyway alf if you get some spare cycles, can you try my
patch & verify that i'm not crazy?
nubbins`: i haven't verified that you necessarily need to apply the dns snip
patch for it to compile on gentoo
assbot: Logged on 15-11-2014 00:34:02; asciilifeform: but i will not be signing any
patch that i can't apply with my mind, in my mental model of the code.
nubbins`: jurov yeah i stupidly attached the shasum of my
patch file to the filename
nubbins`: should have a
patch on the ml in an hour or so, probably poison but feel free to give it a look
nubbins`: they all appear to have the boost:: prefix except for the couple of instances in above
patch assbot: Logged on 02-04-2015 21:54:54; asciilifeform: i never got around to shitting out a
patch to remove the hardcoded seedz
assbot: Logged on 02-04-2015 15:17:35; asciilifeform: my dns seed snip
patch never made it in the realease, did it
danielpbarron: cazalla,
Patch.com reports the arrest of a Massachusetts man who sort to purchase a firearm << should be "sought to purchase" ?
nubbins`: <+asciilifeform> the integer retardation
patch includes the one from portatron <<< o look
jurov: (context: i was hired to
patch android system. had to create nigbuntu lxc container for its monstrous build system)
nubbins`: asciilifeform haven't peeked at your latest mail yet, but applying the portatronic
patch turns my uint32_t error into an int64_t error
mod6: next part here... in your email, it seems that you apply your
patch "asciilifeform-kills-integer-retardation.
patch", and this doesnt seem to completely solve it...
ascii_field: including stdint.h (as per my
patch) in util.h gives
ascii_field: the new static build won't crank even with my
patch.
ascii_field: 'util.h:650:8: error: ‘uint32_t’ does not name a type' without
patch nubbins`: ascii_field you're saying 0.5.3.1-RELEASE won't compile /and/ it won't compile after you merge your portatronic
patch?
nubbins`: nothing else from your portatronic
patch is in 0.5.3.1