I previously wrote:
>It seems --date always uses UTC instead of the user's timezone.
The issue seems a little more complicated than this; I observe that
specifying today's date along with the time picks up that we are in
British Summer Time, and gets the correct timezone offset.
With only a time specified, timezone is incorrectly +0000:
% git ci -m test --date='16:00:00'
[master (root-commit) 2c8ea98] test
Date: Mon Apr 6 15:00:00 2015 +0000
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 f
With a date and time specified, timezone is correctly +0100:
% git ci --amend --date='2015-04-06 16:00:00'
[master 534ec11] test
Date: Mon Apr 6 16:00:00 2015 +0100
1 file changed, 0 insertions(+), 0 deletions(-)
create mode 100644 f
So my assumption the parser would do the right thing with today's date
if I only specified the time seems to be the cause of the problem.
I hope the reader will agree this is rather counterintuitive behaviour.
It seems reasonable to expect that the user who specified only a time
meant "that time today", and the software would act exactly the same way
as it does when today's date is written explicitly.
Finally, I wonder if this might be the same as / related to #762585.
--
http://rjy.org.uk/
--
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
