<whitequark>
this is pretty much the best possible case. I'm running it way outside the specs (all the components are, in principle, rated at 0..-20°C evap temperature), it does match vendors' spec at 0-10°C, it matches my design expectations, and it should work for any application I had in mind
<whitequark>
so I'm declaring this a success.
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 246 seconds]
sandeepkr_ has joined #m-labs
rohitksingh has quit [Read error: Connection reset by peer]
klickverbot has joined #m-labs
<rjo>
whitequark, sb0: anybody opposed to merging release-1 back into master?
sandeepkr__ has quit [Ping timeout: 248 seconds]
kuldeep has quit [Ping timeout: 250 seconds]
<sb0>
rjo, why not cherry-pick the master commits into release-1?
<sb0>
and I don't understand why you'd want to merge release-1 into master
klickverbot has quit [Ping timeout: 246 seconds]
<rjo>
sb0: the master -> release-1 cherry-picking is unaffected by this.
<rjo>
that's completely orthogonal
<sb0>
so what does it do?
<rjo>
the cherry-picking does what it always does. merging release-1 back into master a) ensures that there is nothing in release-1 that is _not_ in master and b) resolves the versions from master being lexically lower than those from release-1
<rjo>
s/lexically/conda-version-sorted/
<sb0>
you can do "git diff release-1..master" and check manually
<sb0>
it's not very complicated
<rjo>
try that yourself.
<sb0>
I did
<sb0>
and except for the compiler, master and release-1 are in sync
<rjo>
then you were sloppy looking at that patch
<sb0>
there must be something new then. what change did i miss?
<rjo>
take a look and read the 4773 additions and 3165 deletions
<sb0>
most of them will be gone after the compiler is merged
<rjo>
there is the browser, all the renaming (which completely breaks reading the patch)
<sb0>
I don't trust git conflict handling will do that in a nicer way
<rjo>
the compiler is hopefully _not_ merged.
<rjo>
maybe you don't. i did it, checked and it was spot on.
kuldeep has joined #m-labs
sandeepkr__ has joined #m-labs
klickverbot has joined #m-labs
sandeepkr_ has quit [Ping timeout: 268 seconds]
klickverbot has quit [Ping timeout: 246 seconds]
<sb0>
and more importantly: I don't trust it won't mess something up
<whitequark>
if rjo says he checked the patch, merge it
<whitequark>
git does mess up things but very rarely, there have been maybe five such instances in my massive series of merges that brings the OR1K backend up to 3.8.1
<whitequark>
well, it's not "git messes things up"
<whitequark>
it's "the merge is ambiguous and the wrong code ends in the branch"
<whitequark>
but release-1 and master are nowhere that level of divergence
<rjo>
maybe this is not clear: merging release-1 into master is supposed to result in zero lines changed in master.
FabM has quit [Quit: ChatZilla 0.9.92 [Firefox 45.0.1/20160315153207]]
<whitequark>
oh
<whitequark>
ok, I understand better now what do you want to do
<whitequark>
sure, do it, I don't see how it can go non-obviously wrong.
evil_spirit is now known as evilspirit
<sb0>
whitequark, if you have a class that contains a host function, an instance of that class is an attribute of object X, and a kernel in X calls self.attr.host_function()
<sb0>
what happens?
<sb0>
if attr is kernel_invariant, does it do the RPC? and if not?
<whitequark>
kernel_invariant does not affect RPCing
<whitequark>
the only thing kernel_invariant semantically does is it prevents writes to attributes specified as such, from within the kernel
<whitequark>
and yes, in this case the function will be RPC'd
<whitequark>
or at least it should
FabM has joined #m-labs
fengling has quit [Quit: WeeChat 1.4]
rohitksingh has joined #m-labs
evilspirit has quit [Read error: Connection reset by peer]
klickverbot has joined #m-labs
klickverbot has quit [Ping timeout: 260 seconds]
evilspirit has joined #m-labs
sandeepkr_ has joined #m-labs
kuldeep has quit [Ping timeout: 250 seconds]
sandeepkr__ has quit [Ping timeout: 264 seconds]
evil_spirit has joined #m-labs
evilspirit has quit [Disconnected by services]
evil_spirit is now known as evilspirit
kuldeep has joined #m-labs
evilspirit has quit [Ping timeout: 250 seconds]
evilspirit has joined #m-labs
rohitksingh has quit [Quit: Leaving.]
_rht has quit [Quit: Connection closed for inactivity]