146700+ entries in 1.105s
mircea_popescu: people used to try and suck producer cock to "be
a tv star"
ascii_field: BingoBoingo: i still don't get it, why was it necessary to shit in
a bath tub ?
mircea_popescu: there was an issue where pre created
a new line. why ? FUCK YOU FOR USING THINGS THATS WHY
mike_c: Feels like
a line-ending problem. dpaste the original?
mike_c: sheesh, put
a semicolon at the end :)
trinque: mircea_popescu: that one I said, if you want
a scrollbar
mircea_popescu: the pill for this would be : never ever sign
a cleartext with lines longer than the signature.
ascii_field: btw there is
a pretty fine british translation
assbot: Logged on 05-08-2015 06:40:49; BingoBoingo: My misdemeanor case is on
a one way path now. It is going to hearing seeking dismissal. If not dismissed then to trial seeking not-guilty adjudication. Then to civil court seeking damages for seriously hindering my employability.
shinohai: I'm still not at
a level where I can cross-compile. So I have
a rather useless box atm.
ascii_field: there's
a fella somewhere who wrote an 'arm' version, if any aficionados of that arch are reading this
ascii_field: my imaginary bitcoin book was to be
a work of 'literate programming'
ascii_field: mircea_popescu is
a fan of knuth's 'literate programming' ?
assbot: Logged on 05-08-2015 04:55:30; ben_vulpes: no! for it is
a merely
a derpy directory structure issue that any sophomore can figure out
BingoBoingo: mircea_popescu: Yeah been going on for
a couple hours nao
mircea_popescu: this incidentally would be
a pretty great equivalent of old style personality cult bs. all os must contain picture of stalin. once he dies, computing takes day off while everyone recompiles new picture in. for everything.
mod6: shinohai: excellent work! thank you. these are the first steps in
a series of similar things needed.
ascii_field played privately with
a mircea_popescu (from log linez) shannonizer
mod6: <+ascii_field> mod6: i'm willing to re-create all of mine << ok no rush here. lemme just re-read and think about all of these things for
a bit.
trinque: putting the information to construct the tree in the patches themselves has
a nice decentralized nature to it
mod6: i gotta think about it
a bit
ascii_field: which
a robotic graphatron could then walk
ben_vulpes: poor mod6 can't catch
a break around here
hanbot: mod6: ;;later tell hanbot ping me when you get
a chance plz. thx! << heya, i've got one
mod6: i need to re-read all of the logs from today and have
a nice long "think" about it.
ascii_field: this magic pill lets you take
a bag of patches, and determine in what order they apply
mod6: ok forget that im still confused for
a moment because im dumb, and maybe I'll just get it in
a few minutes...
mod6: I think I need to see
a concrete example of this - end to end. I just can't picutre it mentally.
jurov: maybe we end up all using
a script to put the package together and sign it.. but in this case it can just output an email message to be just fed to sendmail
assbot: Successfully added
a rating of 1 for n6 with note: crusty blood
mod6: gnupg tries to escape lines that begin with
a dash
mod6: as you can see clearsign mangles the text: - ---
a/rotor.sh .... - -../dist/configure
mod6: it still doesn't help me view
a base64 encoded submission to the deedbot
ben_vulpes: n6: i understand that this is not
a welcome message.
mod6: that's fine, but what if I just wanna look through the submitted patches in deedbot? i now have to do
a bunch of extra gyrations to even see the text
punkman: yeah it's
a base64 blob that includes file and signature when you --sign --armor
trinque: where it's
a wad o... what, base64?
trinque: danielpbarron: yeah but you can do
a sig in similar fashion
mod6: i've been thinking alot about the ML issues that have been brought up lately. and lastnight I bascially came up with: Mailing list
A: for all submissions testing or experimental or otherwise.. Mailing list B: for accepted, signed and released patches, in order. And jurov's /patch.html (or w/e its called) should draw from there.
trinque: I gotta depart to
a meeting, but to summarize I have no strong opinion that deedbot is the solution
trinque: thought gpg could wad
a sig and
a file together in other ways than clearsign
mod6: will deedbot take 2 parameters,
a non-signed .patch file and
a detached signature and somehow colese them?
trinque: mod6: heh I did the site with
a nod to the foundation's
mod6: i also like how it lines up the signatures to
a specific hash horizontally
ascii_field: 'Ada 95: The Lovelace Tutorial.' David
A. Wheeler << probably the most n00bish
mod6: ;;later tell hanbot ping me when you get
a chance plz. thx!
gernika: punkman - I have the Ada 95 reference manual. Seems thorough. Also you can print out
a copy of the GNAT User's Guide at Kinkos - which I've also done. Haven't actually made any progress in reading it but... Seems good by looking at TOC.
punkman: I grabbed
a random Ada book last week, it was awful. need to look again
ascii_field: punkman: perhaps if you ask mircea_popescu nicely, he'll give you
a copy
punkman:
a standalone Ada wallet would be an interesting project
danielpbarron: I also like the idea of
a webpage (maybe
a wiki) that organizes it all, linking to the deeded content of course
jurov: if
a big problem, you can always rebase and rerelease
punkman:
a question that future patch submitters might have: should I patch against last release or most active branch?
assbot: [bitcoin-dev] "
A Transaction Fee Market Exists Without
a BlockSize Limit"--new research paper suggests ... (
http://bit.ly/1OQSsXP )
assbot: Logged on 05-08-2015 15:24:59; punkman: I don't want another VCS system. I just need
a way to import patches in my existing VCS.
trinque: the requirement that signed and deeded patches be the primary representation of
a contribution great appeal though, for obvious reasons
☟︎ punkman: I don't want another VCS system. I just need
a way to import patches in my existing VCS.
☟︎ trinque: implementing
a VCS isn't rocket science; it's just
a matter of getting the abstractions right
trinque: and then maybe deedbot farts out additional nav controls on the html versions of these interesting deeds with
a particular sexp in them
trinque: I probably missed one, and they also divide into further classifications, ref for example can be
a tag, branch, stash
trinque: so, git does it this way: there are Blobs, which are
a k/v pair of which the k is the hash of the v; blobs can be one of: Reference, Commit, Tree, Blob
jurov: how would it look for user? got
a .txt,
a .patch , now what?
trinque: one thing that would be needed on my end is
a saner URL for
a given deed; it needs to just be the hash
trinque: you could implement the data structures needed for VCS atop deedbot in
a similar manner
trinque: the way git handles this is that "everything's
a Blob" then "some Blobs are
a Tree which points to n Blobs which may be Trees or Blobs"
jurov: yes the signed email + extra signed attachs is
a kludge
trinque: no reason I can't add some html nav around that
a la dpaste
trinque: to date I've tried to keep it simple, hence the deeds are plain textfiles linked to by
a single index
mircea_popescu: this readily enforces the two restraings we want enforced, which is :
a) wot restricted and b) signed permanently.
mircea_popescu: this all makes me feel
a lot better about my life expectancy.