Re: [RFC PATCH v1] telemetry design overview (part 1)
- From
Jeff King <peff@peff.net>
- Date
- Jun 8, 2018, 09:07 UTC
- Message-ID
- <20180608090758.GA15112@sigill.intra.peff.net>
- In-Reply-To
- <c3ed8128-1184-8199-06e5-a4e96b2bc7c5@kdbg.org>
On Thu, Jun 07, 2018 at 11:10:52PM +0200, Johannes Sixt wrote:
Show 11 quoted lines
> Am 07.06.2018 um 16:53 schrieb git@jeffhostetler.com: > > From: Jeff Hostetler <jeffhost@microsoft.com> > > > > I've been working to add code to Git to optionally collect telemetry data. > > The goal is to be able to collect performance data from Git commands and > > allow it to be aggregated over a user community to find "slow commands". > > Seriously? "add code to collect telemetry data" said by somebody whose email > address ends with @microsoft.com is very irritating. I really don't want to > have yet another switch that I must check after every update that it is > still off.
If you look at the design document, it's off by default and would write to a file on the filesystem. That doesn't seem all that different from GIT_TRACE.
-Peff