On Thu, 26 Feb 2015 20:55:56 +, str4d wrote:
...
If you only want to force UTC for occasional commands then just add
TZ=UTC in front of the command, but I personally prefer redefining
the git command like above, to prevent accidentally forgetting.
You could also set your entire system to
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Ben Tasker wrote:
- Is the timezone included in commit timestamps?
Yes.
You can override this behaviour, but it's not particularly
convenient to do:
git commit --date=2015-02-25T01:00:00+ -m fixed it
You could probably create an
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA512
Hi,
I'll have to put some files on github.
Has someone done an analysis of git over Tor already?
- - Is the timezone included in commit timestamps?
- - What other (metadata) is potentially leaked?
- - Are there best practices when using git(hub)
Nusenu nus...@openmailbox.org writes:
Has someone done an analysis of git over Tor already?
Not that I'm aware, but that'd be cool.
- Is the timezone included in commit timestamps?
Yes.
- What other (metadata) is potentially leaked?
Beware that there are both committer and author email
- Is the timezone included in commit timestamps?
Yes.
You can override this behaviour, but it's not particularly convenient to do:
git commit --date=2015-02-25T01:00:00+ -m fixed it
You could probably create an alias within git to save typing, though you'd
still have to get used to using
