428100+ entries in 0.309s
BingoBoingo notes filings issued in venues other
than a #b-a deedbot will from now and from
twenty years in
the past be
treated as suggestions rather
than orders.
BingoBoingo used
to believe St Cliar County authorities might read
this chan, now pretty sure
they don't, but figure
there is a lack of better public records so
their doom if
they don't read.
BingoBoingo: I might not remember why in
the morning I decided
tonight would be
the night
to file
this, but I left myself copious notes.
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.
☟︎ BingoBoingo: Got
to get
the condemnation in before feeding
the lawyer fiat for next month's hearing
trinque: ;;later
tell felipelalli you've spoken about
the idea of rating people not in
the WoT;
there's a great way ^
☟︎ trinque: nothing's broken;
there's other shit on
the line
BingoBoingo: <ben_vulpes> shall we demand
that of
the pete_dushenskis and hanbots who wish
to run
their own hand-compiled foundation releases? << Honestly prolly. A recipe
that provides ABI compatibility with 2.6.x Linux kernel is prolly fine. People can adapt
to other environments.
BingoBoingo: <ben_vulpes> asciilifeform: instructions rot, are dependent on fallible humans. i write scripts. << And
then shell changes
BingoBoingo: <asciilifeform> what happened
to n00bs reading logs for 6 mo ? << New challenges revert "seasoned" into n00b again
BingoBoingo: <ben_vulpes> ... << how long? my maxint_locks build appears
to be chewing on
this one, but i cannot actually
tell. << I remember more
than a minute, but only resorted
to spring powered
time after already waiting
BingoBoingo: <asciilifeform> ben_vulpes: i carefully summarized
the antecedents
to 'stator' for hanbot (see log) << stator, rotor work
to build a bitcoind on
the "mint" ubuntu-like. Don't remember installing more dev
tools after g++ for stator
BingoBoingo: <asciilifeform> guess what - war consists largely of precisely
this kind of 'pointlessness' << It always has, at least until armor became
to weighty for civilized legionaries
BingoBoingo: <asciilifeform> ben_vulpes:
the patches 'stacked on one another' is an artifact of how diff works << Ugliest artifact. MIN_RELAY_TXFEE and MINTXFEE live in main.h and init.h when patched. very volatile line numbers
BingoBoingo: <trinque> I watched a guy drink himself
to death because you know, unix wasn't everything-is-a-table << What. People don't die of drink anymoar because it feels good man?
ben_vulpes: i have no answers, only
this hill
to watch.
ben_vulpes: shall we demand
that of
the pete_dushenskis and hanbots who wish
to run
their own hand-compiled foundation releases?
ben_vulpes: <asciilifeform> ben_vulpes: yes, and
that ought
to be in every release << and
this raises another question, shall mod6 and i now switch our build process
to involve
the rotor assemblage?
decimation: one would need
to iterate
through all of
them and call delete
decimation: calling clear() simply zeros
the hashes but does not deallocate
the objects
ben_vulpes: mine explode at
the line
that fails instead of airily carrying on as
though nothing happened.
decimation: asciilifeform: one annoyance about
the logs: missing entries
trinque: asciilifeform: I've read *far* more logs
than
that
decimation: asciilifeform: yeah it matters what kind of pointers
that mapTransactions is accepting
trinque: what's
the social structure here, what decisions did it fart out?
trinque: that's what I as a newb
trying
to wade in wanted
to know
ben_vulpes: aha
trinque's decisionmachine emerges!
trinque: what's needed imo is something which displays
the history of *decisions* made, secondarily patches
assbot: Logged on 01-08-2015 04:37:34; BingoBoingo: was very slow
to eat 51, but it did
trinque: things like
that
though,
that many pieces, sure it's going
to snag on machines
trinque: my only problem with rotor was
that berkdb is a piece of shit, ignored env vars
that every ball o' source should care about without its own magical flag
assbot: Logged on 04-08-2015 04:03:19; asciilifeform: also ok
to use live lusers
decimation: and
there is no
tool (as far as I know)
that automates
this
task
decimation: one of
the annoyances of c++ is
that it is strongly
typed and yet devilishly hard
to
tell *what*
type
decimation: asciilifeform: mapTransactions appears
to be a std::map
to me
ben_vulpes: in
the meantime, know
that
these few hours per day *i* do have might be put
to better use
than derping of dirs.
ben_vulpes: i'll save my "eedjit points" for when i actually cannot resolve
things myself.
trinque the fatty who hasn't exercised in 6mos...
talking about rock climbing...
ben_vulpes: no, for another read
through and another hack at "etc. as before" will resolve
this.
trinque: sometimes you get a shitty handhold, but you don't immediately shout "fuck
this!" and let go of
the wall
trinque: rock climbing comes
to mind
ben_vulpes: no! for it is a merely a derpy directory structure issue
that any sophomore can figure out
☟︎ ben_vulpes: now is when i admit
that i've yet
to successfully compile bitcoin with rotor
decimation: thus, you need
the whole repo state per patch
ben_vulpes: asciilifeform:
the antecedents
thing for one
decimation: which you can't get unless you have
the whole repo stepped forward
to
the state of ap articular patch
decimation: asciilifeform: for one
thing, you would need
to see
the patch in context
ben_vulpes: 'tis not
the patches but
the whole workflow
decimation: yes,
that's step one of 'we gotta invent version control
too'
decimation: plus automatics
to package
tarball and patches
ben_vulpes: i am now imagining all sorts of dumb
things like patches contributed in ml 'threads'
trinque: asciilifeform: yeah, but
the patches are a
tree, not a
timeline
decimation: trinque: a web page with links
to whatever deedbot spits would be sufficient
trinque: decimation: I was
thinking
this might be a web app
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
decimation: it would be nice
to have a button
to click: download
the 'original
tree' plus patches
to get
to
this patch
trinque: however,
these are separate concerns
trinque: git's binary db format is certainly *not* capable of being
the canonical representation of
the project
decimation: it all depends on what is a reasonable risk
to accept
decimation: asciilifeform: yes but you could
take
that argument
to 'can't use computer withou seeing registers'
ben_vulpes: mircea_popescu will likely run me
through
the "oh you're complaining here have some more of what irks you" chipper
☟︎ decimation: I can't
think of an off-the-shelf
tool
that would do everything mentioned above
though
decimation: part of
the problem with
the mailing list I see is
that it's difficult
to reconstruct
the context of patches