diff always shows timestamps in utc

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Wim wrote:
> Public bug reported:
>
> The text used to print time is inconsistent in bzr log and bzr diff:
>
> # bzr log tools/fish/cli_flags.c
> ------------------------------------------------------------
> revno: 2
> committer: Wim Yedema <***>
> branch nick: X
> timestamp: Thu 2009-11-05 14:06:47 +0100
> message:
> X
> ------------------------------------------------------------
> revno: 1
> committer: Wim Yedema <***>
> branch nick: Y
> timestamp: Wed 2009-11-04 17:30:59 +0100
> message:
> Y
> # bzr diff -r1..2 tools/fish/cli_flags.c
> === modified file 'tools/fish/cli_flags.c'
> --- tools/fish/cli_flags.c 2009-11-04 16:30:59 +0000
> +++ tools/fish/cli_flags.c 2009-11-05 13:06:47 +0000
>
>
> The time stamp for log has +0100 but for diff it has +0000
>

well, the times are the same, the former giving you 17:30:59 +0100 and
the latter giving you 16:30:59 +0000. Which is the same 'world' time. I
wonder if diff always gives UTC times, which is why they are +0000. From
all of my quick tests that is what I see (bzr diff always reports UTC time).

It may even be required for programs that have expectations on the
format string?

John
=:->

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iEYEARECAAYFAkry6EMACgkQJdeBCYSNAAMJiwCeIgyyrgfE7K7DFadrZg6T6K/W
bPsAoLYU+NpxiIqhtui3gw0cdQjFvDf3
=VdT2
-----END PGP SIGNATURE-----

It's true that diff seems to always use utc. I don't know of any specific good reason for it to do that.