--- Day changed Sun Oct 11 2015
00:09 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-jnhrfjtrgballrjp] has joined #bitcoin-core-dev
00:11 -!- challisto [~challisto@unaffiliated/challisto] has quit [Quit: Leaving]
00:16 < GitHub84> [bitcoin] jamesob opened pull request #6804: [tests] Add basic coverage reporting for RPC tests (master...rpc_coverage) https://github.com/bitcoin/bitcoin/pull/6804
00:26 -!- jgarzik_ is now known as jgarzik
00:27 -!- jgarzik [~jgarzik@104-178-201-106.lightspeed.tukrga.sbcglobal.net] has quit [Changing host]
00:27 -!- jgarzik [~jgarzik@unaffiliated/jgarzik] has joined #bitcoin-core-dev
00:41 < jcorgan> cfields: what is the specific issue with #6681
01:21 -!- Arnavion [arnavion@unaffiliated/arnavion] has quit [Quit: Arnavion]
01:22 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
01:23 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
01:23 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
01:26 -!- wumpus [~quassel@pdpc/supporter/professional/wumpus] has joined #bitcoin-core-dev
01:31 -!- Arnavion [arnavion@unaffiliated/arnavion] has joined #bitcoin-core-dev
01:33 < GitHub35> [bitcoin] laanwj pushed 3 new commits to master: https://github.com/bitcoin/bitcoin/compare/b94ae81576c1...4ca6ddec4d79
01:33 < GitHub35> bitcoin/master 28e3249 Wladimir J. van der Laan: Bump minrelaytxfee default...
01:33 < GitHub35> bitcoin/master 4e2efb3 Wladimir J. van der Laan: tests: update transaction_tests for new dust threshold
01:33 < GitHub35> bitcoin/master 4ca6dde Wladimir J. van der Laan: Merge pull request #6793...
01:33 < GitHub99> [bitcoin] laanwj closed pull request #6793: Bump minrelaytxfee default (master...2015_10_bump_minrelaytxfee) https://github.com/bitcoin/bitcoin/pull/6793
01:37 < GitHub2> [bitcoin] laanwj pushed 1 new commit to 0.10: https://github.com/bitcoin/bitcoin/commit/842c48dba39e9ad7a74d21106a67e047e3d79ced
01:37 < GitHub2> bitcoin/0.10 842c48d Wladimir J. van der Laan: Bump minrelaytxfee default...
01:38 < GitHub198> [bitcoin] laanwj pushed 1 new commit to 0.11: https://github.com/bitcoin/bitcoin/commit/e7bcc4aac3a1a2b62d53c0261e803786123477a8
01:38 < GitHub198> bitcoin/0.11 e7bcc4a Wladimir J. van der Laan: Bump minrelaytxfee default...
01:45 < wumpus> going to tag rc2 for 0.11.1 and 0.10.3 in a min
01:47 < GitHub69> [bitcoin] laanwj pushed 1 new commit to 0.11: https://github.com/bitcoin/bitcoin/commit/dad3e98e8f4d2efdcad947631a48b520f01f822e
01:47 < GitHub69> bitcoin/0.11 dad3e98 Wladimir J. van der Laan: doc: update release notes for 0.11.1rc2
01:47 < wumpus>  * [new tag]         v0.11.1rc2 -> v0.11.1rc2
01:49 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Ping timeout: 250 seconds]
01:49 < GitHub186> [bitcoin] laanwj pushed 1 new commit to 0.10: https://github.com/bitcoin/bitcoin/commit/8d598c26e34e36619180f73926043a43bfe68879
01:49 < GitHub186> bitcoin/0.10 8d598c2 Wladimir J. van der Laan: doc: Update release notes for 0.10.3rc2
01:50 < wumpus>  * [new tag]         v0.10.3rc2 -> v0.10.3rc2
01:52 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
01:55 -!- Thireus1 [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
01:55 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Remote host closed the connection]
02:04 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
02:04 -!- Thireus1 [~Thireus@icy.thireus.fr] has quit [Remote host closed the connection]
02:09 -!- challisto [~challisto@c-76-16-149-33.hsd1.il.comcast.net] has joined #bitcoin-core-dev
02:09 -!- challisto [~challisto@c-76-16-149-33.hsd1.il.comcast.net] has quit [Changing host]
02:09 -!- challisto [~challisto@unaffiliated/challisto] has joined #bitcoin-core-dev
02:14 -!- fanquake [~Adium@unaffiliated/fanquake] has joined #bitcoin-core-dev
02:29 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Remote host closed the connection]
02:30 < fanquake> wumpus how soon do you want to release 0.11.1 ? 
02:30 < wumpus> at least want to have 0.11.1rc2 out asap
02:31 < wumpus> can't really predict what the rc process will bump into, but obviously the final release should be as soon as possible too
02:31 < fanquake> Fair enough. I'll have some sigs up shortly.
02:33 < michagogo> wumpus: did you see my earlier messages?
02:33 < wumpus> michagogo: yes -> version bump was forgotten in rc1
02:33 < michagogo> Ah, I see
02:33 < wumpus> should be ok now
02:33 < michagogo> Also re: the VM upgrades
02:34 < wumpus> don't know about the rest of your VM issues, shouldn't have changed AFAIK
02:34 < michagogo> And the 0.10 dir name
02:34 < michagogo> Yeah, I didn't have any issues
02:34 < wumpus> a few people submitted signatures so it seems to have worked
02:34 < michagogo> Was responding to you talking about it taking a long time to upgrade
02:34 < wumpus> oh yes it takes long
02:34 < fanquake> Yea I didn't have any issue building 0.11.1rc1
02:35 < michagogo> wumpus: so yes, on KVM recreating the VM should make it not take so long, afaik
02:35 < wumpus> michagogo: so your take is that creating new images wouldn't makke it faster?
02:35 < wumpus> michagogo: oh it would?
02:35 < michagogo> wumpus: on KVM, I think it should make it faster
02:36 < michagogo> You also may be able to upgrade the base image, I'm not sure
02:36 < wumpus> but in image generation there isn't much of a difference between LXC and KVM, I think the only difference is grabbing a partition at the ned
02:36 < michagogo> wumpus: no, that changed
02:36 < wumpus> okay
02:36 < michagogo> LXC used to create a KVM image and extract it
02:36 < wumpus> yes
02:36 < michagogo> (With vmbuilder)
02:37 < michagogo> Now it uses debootstrap directly
02:37 < wumpus> that's changed now?
02:37 < michagogo> The unfortunate side effect is that the LXC it generates is only packages from precise
02:37 < michagogo> And not from -updates and -security
02:37 < wumpus> isn't that a matter of changing the command?
02:38 < michagogo> wumpus: well, it's a different process generating it
02:38  * wumpus doesn't know mjuch about debootstrap, I used it to bootstrap debian on ARM boards, but just followed instructions
02:38 < michagogo> Vmbuilder uses debootstrap as a component, I think
02:38 < michagogo> I don't remember exactly why the change was made
02:38 < michagogo> I think the old method was causing some issues
02:39 < michagogo> This way works pretty smoothly, except for the fact that it doesn't include packages from -security/-updates
02:39 < michagogo> So you need to do this: https://www.irccloud.com/pastebin/vHn9M0LP
02:41 < michagogo> That should be adaptable for KVM, or you can just recreate the base image
03:01 < wumpus> thanks, I'll give it a try
03:05 < fanquake> wumpus would you be able to merge my two sets of sigs for rc1 & rc2 ?
03:07 < wumpus> fanquake: sure
03:08 < fanquake> I'm building the 0.10 rc now
03:08 < fanquake> Cheers
03:11 < michagogo> Are we doing the detached signing?
03:11 < wumpus> michagogo: for 0.11 we are, not sure about 0.10 (but I think so)
03:11 < michagogo> I mean specifically the RCa
03:12 < michagogo> RCs*
03:15 < wumpus> for rc2 there will be detached sigs, for rc1 we don't bother because of the lack of version bump and it became superseded so fast
03:30 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
03:32 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 240 seconds]
03:43 -!- nartac [~nartac@2607:fcd0:100:2300::e8a2:c5c2] has joined #bitcoin-core-dev
03:44 < nartac> if count of forked coin wallets will be >50%. Is it mean new coins will get all old coins wallets 
03:47 -!- BashCo_ [~BashCo@unaffiliated/bashco] has quit [Ping timeout: 268 seconds]
03:48 -!- BashCo [BashCo@gateway/vpn/mullvad/x-bdjxdtdwlajtgjdi] has joined #bitcoin-core-dev
03:49 < wumpus> nartac: sounds like a #bitcoin question
03:50 < wumpus> michagogo: your instructions almost worked - for KVM you need a start-target in there somewhere
03:57 < wumpus> ...and a stop-target at the end, before copying
03:59 < wumpus> oh, but I get a new error now:  Could not open 'base-precise-amd64.qcow2': Too many open files
04:00 < wumpus> it gets in a loop
04:00 < wumpus> well, create a new image it is
04:18 -!- ParadoxSpiral [~ParadoxSp@p508B9840.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
04:43 < michagogo> wumpus: yeah, makes sense. I think I mentioned (or if not, I meant to mention) that for KVM, you probably need to adapt the instructions. I think the command for making the image copy is different too, not just a cp -- take a look at make-clean-vm.
04:44 < wumpus> michagogo: yes, I naively thought it worked - almost literally - for KVM, but that was only apparantly. The qcows keep a reference to the base image, so copying the result back to the base image creates an infinite loop
04:45 < michagogo> Ah. Yeah, so it's an actual snapshot/forked clone mechanism.
04:46 < michagogo> So just reversing the command used in make-base-vm wouldn't work either, but I'm sure it's possible to do the same thing if you know how to use the tools.
04:48 < wumpus> I think most straightforward would be to start the vm using the base image directly, then upgrade that, skip the copy/move step at the end
04:48 < michagogo> Anyway, for KVM, you're probably just better off creating a new image anyway. If I'm not mistaken, when you upgrade the base image, something about the way the upgrade process works means that the automatic upgrade as part of the building is broken and that breaks the whole build, so you need to repeat the upgrade process every time anything updates
04:49 < wumpus> right
04:49 < michagogo> Yeah, probably. I just don't know enough about KVM to get into that… And I'm running inside a VM anyway, so I'm stuck with LXC
04:49 < michagogo> With KVM, you can just create a new base image and be done with it, whereas with LXE you have to do the whole upgrade-the-base thing because of the debootstrap switch.
04:50 < wumpus> I first accidentally created a lxc image, that takes quite a bit longer
04:51 < michagogo> Eh? LXC should take less time than KVM
04:51 < michagogo> Or maybe not, I don't remember all the details.
04:51 < michagogo> Anyway, g2g... In a couple hours hopefully I can get someone to boot my computer, remote in and kick off the rc2 builds.
04:52 < michagogo> (Oh, and just to make sure: you saw my note about the wrong release name for 0.10-win, right?)
04:53 -!- BashCo [BashCo@gateway/vpn/mullvad/x-bdjxdtdwlajtgjdi] has quit [Ping timeout: 265 seconds]
04:58 < wumpus> michagogo: hm? 
04:58 < wumpus> nothing should have changed there
05:00 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
05:02 < wumpus> oh I see now, using the wrong windows dirname in my script
05:03 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 268 seconds]
05:06 -!- BashCo [~BashCo@unaffiliated/bashco] has joined #bitcoin-core-dev
05:14 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
05:16 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds]
05:19 < GitHub31> [bitcoin] btcdrak opened pull request #6805: Create btcdrak-key.pgp (master...btcdrakpgp) https://github.com/bitcoin/bitcoin/pull/6805
05:43 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
05:48 < wumpus> michagogo: removed my 0.10.3rc1 win sigs, indeed, 0.10 was pre-detached windows signatures
06:32 -!- belcher [~user@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
06:33 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
07:06 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
07:08 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds]
07:09 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Max SendQ exceeded]
07:10 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
07:17 -!- sipa_ is now known as sipa
07:23 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
07:26 < fanquake> btcdrak Have you contributed a gitian build to the sigs repo?
07:28 < btcdrak> I'm just building 0.10.3rc2 now
07:29 < michagogo> wumpus: yeah, it's a good thing that Friday night I ran the 0.11 build and not the 0.10 build. I only realized later that I probably had to tweak the script for it to do 0.10 right.
07:59 -!- moli [~molly@unaffiliated/molly] has quit [Read error: Connection reset by peer]
08:12 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
08:16 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has joined #bitcoin-core-dev
08:24 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
08:38 -!- nartac [~nartac@2607:fcd0:100:2300::e8a2:c5c2] has left #bitcoin-core-dev []
08:45 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
09:25 -!- PaulCape_ [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
09:27 -!- PaulCapestany [~PaulCapes@204.28.124.82] has quit [Ping timeout: 250 seconds]
09:38 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
09:48 < fanquake> wumpus Your sig is missing from the 0.10.3rc2 osx dir
09:48 < wumpus> fanquake: huh, will add
09:55 < fanquake> Anyone running osx 10.11 that can test mounting the latest RC ? See #6800
10:01 -!- fanquake [~Adium@unaffiliated/fanquake] has quit [Quit: Leaving.]
10:15 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
10:18 < michagogo> Side note: I'm kinda surprised nothing breaks when a gitian build is running in LXC in Ubuntu in Virtualbox in Windows and Windows hibernates
10:30 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
10:36 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]
10:37 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
10:40 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
10:55 < michagogo> -Whois cfields cfields
10:55 < michagogo> ...
10:56 < michagogo> Oops
10:57 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
11:02 < tripleslash> michagogo, that's quite the chain of environments
11:03 < michagogo> tripleslash: it's really just 3 layers
11:03 < michagogo> LXC in VM
11:03 < michagogo> But yeah
11:04 < michagogo> wumpus: are you able to detached-sign, or does cfields need to do it?
11:07 < michagogo> Hm, gitian idea: an option to select inputs dir
11:08 < michagogo> Could help avoid issues like building multiple versions before detached sigs are posted
11:18 < tripleslash> I can't speak for Virtualbox, but having used Hyper-V extensively, I know it to be very resilient with regard to suspensions.
11:33 -!- ParadoxSpiral_ [~ParadoxSp@p508B8DE1.dip0.t-ipconnect.de] has joined #bitcoin-core-dev
11:36 -!- ParadoxSpiral [~ParadoxSp@p508B9840.dip0.t-ipconnect.de] has quit [Ping timeout: 265 seconds]
11:44 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 246 seconds]
11:45 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
12:02 -!- challisto [~challisto@unaffiliated/challisto] has quit [Quit: Leaving]
13:02 < michagogo> Okay, 0.10.3rc2 should be PR'd soonish
13:02 < sipa> PRd?
13:03 < sipa> oh, gitian sigs :)
13:03 < michagogo> Giti-yeah
13:03 < btcdrak> I signed too
13:18 -!- BananaLotus [~BananaLot@54.186.186.141] has quit [Read error: Connection reset by peer]
13:18 -!- guruvan [~guruvan@unaffiliated/guruvan] has quit [Read error: Connection reset by peer]
13:19 -!- paveljanik [~paveljani@unaffiliated/paveljanik] has quit [Quit: Leaving]
13:30 -!- guruvan [~guruvan@unaffiliated/guruvan] has joined #bitcoin-core-dev
13:30 -!- BananaLotus [~BananaLot@54.186.186.141] has joined #bitcoin-core-dev
13:47 < michagogo> Correction: they've been added to my 0.11.1rc2 PR.
14:16 < Luke-Jr> are rc2s tagged?
14:17 < sipa> yes
14:21 -!- Thireus [~Thireus@icy.thireus.fr] has joined #bitcoin-core-dev
14:53 -!- CodeShark [~CodeShark@cpe-76-167-237-202.san.res.rr.com] has quit [Ping timeout: 246 seconds]
15:18 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
15:18 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
15:18 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Client Quit]
15:23 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
15:26 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
15:53 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has quit [Ping timeout: 240 seconds]
15:54 -!- zxzzt [~prod@static-100-38-11-146.nycmny.fios.verizon.net] has joined #bitcoin-core-dev
16:01 < PRab> Is there a proper procedure for updating your gitian gpg key? My old one expired and I noticed that new stuff has been tagged, so I was going to build it.
16:14 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
16:16 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
16:42 < GitHub37> [bitcoin] PRabahy opened pull request #6806: Updating my GPG key because my old one expired. (master...NewGPG) https://github.com/bitcoin/bitcoin/pull/6806
16:48 < GitHub128> [bitcoin] PRabahy closed pull request #6806: Updating my GPG key because my old one expired. (master...NewGPG) https://github.com/bitcoin/bitcoin/pull/6806
16:49 < Luke-Jr> PRab: just update your current key to expire later..
16:49 < PRab> Luke-Jr: I wanted to go to an online/offline scheme.
16:50 < PRab> I think I came up with a reasonable solution, but messed up the PR a little.
16:50 < Luke-Jr> btw: are there detached sigs yet?
16:51 < Luke-Jr> cfields: ^
16:51 < GitHub41> [bitcoin] PRabahy opened pull request #6807: Updated Prab's PGP Key (master...NewGPG) https://github.com/bitcoin/bitcoin/pull/6807
16:52 < PRab> There we go, that looks good to me. The commit contains data signed by both the old and new key, so once its merged there is permanent proof that I control both keys.
16:52 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
16:52 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Max SendQ exceeded]
16:53 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
16:54 < Luke-Jr> PRab: next time just update the same PR with the new branch..
16:54 < PRab> I couldn't do a force push through SourceTree, so that was easier.
16:55 < Luke-Jr> :/
16:57 -!- belcher [~user@unaffiliated/belcher] has quit [Read error: Connection reset by peer]
16:58 -!- molly [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
16:59 -!- belcher [~user@unaffiliated/belcher] has joined #bitcoin-core-dev
17:01 -!- moli [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
17:02 -!- PaulCape_ [~PaulCapes@204.28.124.82] has quit [Quit: .]
17:02 -!- PaulCapestany [~PaulCapes@204.28.124.82] has joined #bitcoin-core-dev
17:14 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-jnhrfjtrgballrjp] has quit [Quit: Connection closed for inactivity]
17:37 -!- ParadoxSpiral_ [~ParadoxSp@p508B8DE1.dip0.t-ipconnect.de] has quit [Remote host closed the connection]
17:43 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
18:25 -!- belcher [~user@unaffiliated/belcher] has quit [Quit: Leaving]
18:38 < Luke-Jr> k, done w/ sigs
18:39 < jgarzik> Corrections welcome: https://www.reddit.com/r/Bitcoin/comments/3oecqm/psa_to_address_mempool_flooding_bitcoin_core/
18:39 < jgarzik> Perhaps duplicative, but another one didn't stick
18:57 < tripleslash> and already seized on by a troll that you didn't provide enough warning. :-/
18:59 < phantomcircuit> jgarzik, ha yeah that brough ina bunch of /xt trolls
18:59 < phantomcircuit> shocking
19:05 < jcorgan> why bother with /r/bitcoin anymore?
19:06 < tripleslash> because it is the defacto?
19:06 < tripleslash> same reason companies still screw with .com when there are plenty of other options
19:08 < alpalp> jcorgan: what are better options?
19:10 < jcorgan> i'm not sure there are any useful public venues for bitcoin related matters any more.  i'd say post announcements on a read-only mailing list, say, bitcoin-core-announce, and let responsible people stay on top of announcements about software they run that handles their money.
19:11 < jcorgan> but posting a PSA and notice and immediately getting troll grief just...sucks.
19:11 < tripleslash> An announcement list is probably long overdue, but then the issues of "Who has post access and what" still come up
19:11 < phantomcircuit> jcorgan, the same group of trolls is everywhere
19:11 < tripleslash> you know whatever is decided won't be enough
19:13 < alpalp> jcorgan: it's a handful of idiots
19:13 < alpalp> who are loud
19:14 < alpalp> one guy who thinks mike hearn warned us of this and would have saved us, and he gets downvoted, its not a big deal
19:14 < alpalp> most of the children have moved out of /r/bitcoin anyway
19:16 < jcorgan> meh.  i don't know why we keep expecting unpaid but skilled and highly productive volunteers to put up with it.
19:17  * jcorgan is grumpy again
19:18 -!- go1111111 [~go1111111@162.244.138.37] has quit [Ping timeout: 246 seconds]
19:26 < tripleslash> jcorgan, thanks for the indirect quote: https://www.reddit.com/r/Bitcoin/comments/3oecqm/psa_to_address_mempool_flooding_bitcoin_core/cvwial1
19:27 < alpalp> What are the odds this guy even runs a node
19:30 < tripleslash> alpalp: he confessed to running xt, so I suppose it depends on your definition of 'node'
19:30 < jcorgan> yeah, assholes are everywhere.  engaging them just adds legitimacy, as if you agree anything they have to say is worth your time to respond.
19:30 < alpalp> tripleslash: I have doubts even 1/4 of those who claim to run xt nodes actually do
19:31 < tripleslash> yeah, I saw the number of people paying to have clones run several months ago
19:34 < jcorgan> guys, sorry for instigating this discussion thread.  clearly this was the kind of thing happening on #bitcoin-dev that brought about the change to using this channel instead.  can we go back to pull requests and releases?
19:35 < tripleslash> +1
19:38 < tripleslash> So there's a .1 coming down to change the default minrelaytxfee?
19:40 < phantomcircuit> jcorgan, ha he deleted his post
19:40 < phantomcircuit> yes we can
19:47 < jcorgan> i'm still interested in understanding what is going on with #6681
19:50 < phantomcircuit> it would be nice if we could unify the memory usage stuff such that there was a single parameter
19:51 -!- moli [~molly@unaffiliated/molly] has joined #bitcoin-core-dev
19:54 -!- molly [~molly@unaffiliated/molly] has quit [Ping timeout: 240 seconds]
20:00 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
20:17  * jgarzik returns from kid night-night
20:17 < jgarzik> would prefer to keep non-tech discussion of my post on #bitcoin.  if there are tech corrections, by all means, post here
20:18 < jgarzik> RE: forum, twitter and reddit can be useful to start getting word out to other forums.  reporters watch them etc.
20:41 < nanotube> hm, set up a twitterbot to tweet bitcoin-announce mailing list titles with links to full email body? :)
21:15 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Ping timeout: 264 seconds]
21:15 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has joined #bitcoin-core-dev
21:22 < tripleslash> nanotube: twitterbot with release notes for builds that have gone wide release
21:33 < nanotube> maybe just the rss feed? https://bitcoin.org/en/rss/releases.rss
21:44 < tripleslash> That works
21:54 -!- maaku [~quassel@botbot.xen.prgmr.com] has quit [Remote host closed the connection]
21:56 -!- maaku [~quassel@botbot.xen.prgmr.com] has joined #bitcoin-core-dev
21:56 -!- maaku is now known as Guest38362
22:13 < GitHub12> [bitcoin] RHavar closed pull request #6649: Default fPayAtLeastCustomFee to false (master...master) https://github.com/bitcoin/bitcoin/pull/6649
22:20 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has quit [Quit: My MacBook has gone to sleep. ZZZzzz…]
22:24 -!- go1111111 [~go1111111@162.244.138.37] has joined #bitcoin-core-dev
22:32 -!- d_t [~textual@c-50-136-139-144.hsd1.ca.comcast.net] has joined #bitcoin-core-dev
22:39 -!- Guest38362 is now known as maaku
23:01 -!- Ylbam [uid99779@gateway/web/irccloud.com/x-crfjzerbwxcvpeyg] has joined #bitcoin-core-dev
23:06 -!- supasonic [~supasonic@172-11-188-117.lightspeed.rcsntx.sbcglobal.net] has quit [Quit: Leaving]
23:09 < wumpus> looking at stack layouts, two functions stand out in bitcoind, secp256k1_ecmult_gen_context_build  with a 221760 byte stack frame and ThreadSocketHandler with 67080. The rest is <8000.
23:11 < wumpus> fortunately, neither is a recursive function 
23:27 -!- Thireus [~Thireus@icy.thireus.fr] has quit [Quit: Leaving.]