Am 09.06.2018 um 08:51 schrieb Jeff King:
I actually think this could be useful for normal users, too. We have GIT_TRACE for dumping debug output, and we sometimes ask users to turn it on to help diagnose a problem (not to mention that we use it ourselves).
The BIG difference is in "we ask the users". Asking for a trace is a one-shot thing; this telemetry thing is obviously intended for long-term survaillance.
AFAICT this telemetry data is the same thing, but for performance. When somebody says "why does this command take so long", wouldn't it be nice for us to be able to tell them to flip a switch that will collect data on which operations are taking a long time?
Why do we need long-term survaillance to answer this question and why can it not be made a mode of GIT_TRACE?
-- Hannes
