--- Log opened Sun Dec 12 00:00:59 2021
08:31 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has quit [Remote host closed the connection]
08:31 -!- elsirion [~quassel@gateway/tor-sasl/elsirion] has joined #bitcoin-rust
11:38 -!- trev [~trev@user/trev] has quit [Quit: trev]
15:56 -!- michaelfolkson [~michaelfo@138.68.143.20] has quit [Ping timeout: 250 seconds]
15:57 -!- michaelfolkson [~michaelfo@138.68.143.20] has joined #bitcoin-rust
16:34 < ariard> BlueMatt: "probably its really delayed and the fee is high so you wont get in" right but closing on a tick timer add a predictible bound compared to block variance, before things are getting worst
16:34 < ariard> anyway maybe easier to sync on that during tmrw meeting :)
19:52 < BlueMatt> ariard: yea, lets chat over voice, but I'm dubious that particular one-block difference ever matters.
22:16 -!- trev [~trev@user/trev] has joined #bitcoin-rust
23:12 < RCasatta[m]> Using the githum-merge.py tool, is there a way to specify githubmerge.testcmd such that it tests every commit in the PR? Interactively I would do something like `git rebase -i --exec "cargo test" 04a8f89f0566e902f7064f428ff8afc247c83ec2~` but how can I specify the starting commit generically?
--- Log closed Mon Dec 13 00:00:59 2021