[15:43:40] bd808: meeting? [15:44:02] anomie: doh. I got lost in a phab response. on my way [17:15:45] anomie: just one thing, autopatrol data is public (we know who has the right) should it still be behind patrol permission checks? [17:15:56] that was the reason I did it in several cases [17:16:51] Amir1: I don't know why the checks are there in the first place. But the existing behavior is that you can't see whether an RC was patrolled or not if you don't have the permission. [17:20:17] Honestly, same for me too. I personally prefer to make autopatrol data more visible (as it's easily obtainable by everyone, you just check the editor's user rights) but if you think it should stay behind walls, fine for me. [17:46:15] I think the reasoning was the same as for watch data: make it hard for clever vandals to identify pages that are not watched [18:40:16] legoktm: ^_^ https://gerrit.wikimedia.org/r/#/c/416619/ [21:15:48] anyone else has trouble git pulling mediawiki/core? [21:16:24] >git pull [21:16:24] fatal: internal server error [21:16:24] remote: internal server error [21:16:24] fatal: protocol error: bad pack header [21:17:43] no_justification: ^ [21:18:03] Try fetching with --prune [21:18:07] Or `git remote prune origin` [21:18:25] This happens when I delete wmf.* branches, you've got said branch locally, then I gc and it deletes [21:18:29] The objects [21:21:33] no_justification: thanks, that helped (`git remote prune origin`) [21:21:35] good to know