And from a person assumed to have no privacy rights by the NSA (since I'm not an American citizen) there's some benefit of that phoned home data existing in a non US legal jurisdiction too... Even if you _don't_ assume Google is currently doing evil, we _do_ know they're subject to PRISM and NSLs...
They used to say that you have to trust the compiler. But not even that is true these days. Perhaps you've read about the secret hdd partitions that the NSA were using.
These days it goes like this: open-source hardware, open-source firmware, open-source compiler, open-source software.
Only when an entity can follow this path to build their own trusted stack can we begin to move with high confidence.
You can't trust the supply chain any more, you can't even trust the silicon unless you made it (and all the machines you used to make it) yourself.
Are you _sure_ that network chip, usb controller, or flash ram you built your open source hardware out of isn't exploited?
If you're on the fence about whether you're "too paranoid" or "not paranoid enough", make sure you've read what some people do for free, just for fun/curiosity/geek-cred/reputation:
http://travisgoodspeed.blogspot.com.au/2012/07/emulating-usb...
http://www.bunniestudios.com/blog/?p=3554
Then imagine what their grey-suited counterparts on 200K salaries at the NSA with (for all intents and purposes) unlimited research budgets might be up to.
I don't claim it's necessarily malicious. The explanation given in the git log makes sense, though there are better ways to accomplish the stated goal, such as replacing Google's tracking URLs with invalid ones. But leaving those changes in public releases of software supposed to increase privacy seems negligent.