(This is also filed at https://bugs.chromium.org/p/git/issues/detail?id=43.) Affected Version: All? This has been bothering me at least a year. What steps will reproduce the problem? 1. Author a commit. 2. "git log --pretty=fuller" What is the expected output? The log will display that the timestamps of the commit have both the author time and committer time in UTC. Internally no part of the commit will have stored any time zone information and when the commit is shared with others no information about where the user was in the world at the time of the commit will be obtainable from it. What do you see instead? Authoring and sharing a commit by default exposes the user's time zone. Additional context: "commit --date=YYYY-MM-DDThh:mm:ss+0000" suffices to put the author time in UTC but not the commit time in UTC. But the user shouldn't have to pass a flag at all. Where the user is in the world is PII that git ought not to record and make available as part of the user's software engineering (make available to colleagues, in the case of proprietary development, and make available to the world, in the case of open source). Git should entirely stop accessing, recording, and sharing the user's time zone, full stop. Failing that, git should by default stop accessing, recording, and sharing the user's time zone, but if individual users want to have their time zones on their commits, they can opt into it. Failing that, users should be able to add a .gitconfig line to ensure that all author timestamps, all committer timestamps, and any other information are in UTC. (Thanks much, -Nathaniel)