Junio C Hamano <gitster@xxxxxxxxx> writes: > And more importantly, I do not see why it should be made impossible > to override per repository/project in a multi-tenant installation. > Some projects may be more "privacy" sensitive than others. Those > who want to use tighter setting should be able to enable it even > when the side-wide default is set to false, no? To answer an inevitable and natural follow-up question preemptively, the primary reason why we have the override => 0 mechanism is so that site administrators can disable certain expensive features (like blame, snapshot, etc.) no matter what each project hosted by them wish. And hiding contributor identity would not be a choice that is based on how expensive the feature is to run.
