--- Log opened Thu Dec 17 00:00:49 2020
04:12 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has quit [Ping timeout: 268 seconds]
06:41 -!- jb55 [~jb55@gateway/tor-sasl/jb55] has joined ##miniscript
06:47 < andytoshi> lemme check, i think it was in the head commit..
06:49 < andytoshi> hmm, now i can't find it. lol, lemme update my scripts to record cargo output on every commit
06:49 < sanket1729> lol
06:49 < andytoshi> i learned about `git-notes` recently so in future you're gonna see a lot more crazy-specific historical claims from me
06:49 < andytoshi> "at this exact second on 2020-12-17, rustc 1.48.0 said this about commit X"
06:50 < sanket1729> sounds interesting!
06:51 < andytoshi> it's actually super cool, you can create indpendent note histories whose tips are recorded in .git/refs/notes/, and internally they have a map from commit IDs to note blobs
06:51 < andytoshi> and you can control which ones appear in `git log` etc
07:59 < sanket1729> andytoshi: so what's the verdict on the warning?
07:59 < andytoshi> if you can't find it then i think it's fine
07:59 < andytoshi> i have been pulled into a couple other things
08:01 < andytoshi> hmm i wonder if i was looking at completely the wrong repo or something... i don't have a record of testing #68. ok lemme do that real quick (it'll take like 10 minutes cuz i run the fuzztests with 100x iterations now, twice)
08:02 < andytoshi> which is probably overkill for a PR that does not actually touch any code :P but process is process
08:03 < sanket1729> lol. should we switch rust-elements to github actions, add lints, rust fmt etc..
08:03 < andytoshi> i would welcome a PR to do that... i probably can't for several hours
08:03 < andytoshi> i'd like ultimately to take stevenroose's PR to just make it a fork of rust-bitcoin
08:03 < andytoshi> but it'll be a while before we can do that
08:04 < andytoshi> lol wtf github "now supports uploading mp4 and mov files", why don't they stop hiding/deleting shit before adding features
08:05 < andytoshi> lol we are missing a bunch of tags on rust-elements
08:06 < sanket1729> I can make a PR for that, but if we are going switch a fork of rust-bitcoin. Might not be worth investing time in large diffs breaking all other PRs etc
08:07 < andytoshi> yeah, agreed, let's not rustfmt for now
08:07 < andytoshi> if you wanna rustfmt shit, you're welcome to find individual files in rust-bitcoin that can be formatted with minimal disruption and add those to CI
08:09 < sanket1729> yeah, going file by file might be best way for rust-bitcoin. But whenever we decide to go steven's fork for rust-elements. We should enforce it at the first initial commit. 
08:11 < andytoshi> well, if we make it a fork then we definitely can't gratuitously modify files like that
08:11 < andytoshi> published rust-elements 0.15 and pushed new tags
08:12 < sanket1729> so, I see some altcoins cherry-pick commits from bitcoin-core as soon they are merged. Is it possible to have something like that setup?
08:58 < andytoshi> yes, we can do that (except not in a stupid way the way that most alts do)
08:59 < andytoshi> but if we run a source formatter over everything (the way a certain stupid altcoin did) then we will have a very bad time of it
08:59 < andytoshi> we do this already for libsecp-zkp
08:59 < andytoshi> i mean, not "as soon as they are merged", but as soon as jonas or i gets around to it....we still want human intervention/review. but it's not hard to do
09:37 -!- jeremyrubin [~jr@c-73-15-215-148.hsd1.ca.comcast.net] has joined ##miniscript
18:10 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has quit [Remote host closed the connection]
18:10 -!- andytoshi [~apoelstra@unaffiliated/andytoshi] has joined ##miniscript
23:16 -!- shesek [~shesek@unaffiliated/shesek] has quit [Remote host closed the connection]
23:57 -!- shesek [~shesek@164.90.217.137] has joined ##miniscript
23:57 -!- shesek [~shesek@164.90.217.137] has quit [Changing host]
23:57 -!- shesek [~shesek@unaffiliated/shesek] has joined ##miniscript
--- Log closed Fri Dec 18 00:00:52 2020