From: Andreas Schwab <schwab@linux-m68k.org>
To: "Mattias Andrée" <maandree@operamail.com>
Cc: git@vger.kernel.org
Subject: Re: [PATCH] CET is only one hour ahead of UTC, it even says so in date.c
Date: Fri, 16 Aug 2013 22:32:46 +0200 [thread overview]
Message-ID: <877gfl1imp.fsf@igel.home> (raw)
In-Reply-To: <1376649800-442-1-git-send-email-maandree@operamail.com> ("Mattias Andrée"'s message of "Fri, 16 Aug 2013 12:43:20 +0200")
Mattias Andrée <maandree@operamail.com> writes:
> diff --git a/Documentation/date-formats.txt b/Documentation/date-formats.txt
> index c000f08..4dbaafa 100644
> --- a/Documentation/date-formats.txt
> +++ b/Documentation/date-formats.txt
> @@ -11,11 +11,11 @@ Git internal format::
> It is `<unix timestamp> <timezone offset>`, where `<unix
> timestamp>` is the number of seconds since the UNIX epoch.
> `<timezone offset>` is a positive or negative offset from UTC.
> - For example CET (which is 2 hours ahead UTC) is `+0200`.
> + For example CET (which is 1 hour ahead UTC) is `+0100`.
>
> RFC 2822::
> The standard email format as described by RFC 2822, for example
> - `Thu, 07 Apr 2005 22:13:13 +0200`.
> + `Thu, 07 Apr 2005 22:13:13 +0100`.
This timestamp cannot be in the CET timezone, though.
Andreas.
--
Andreas Schwab, schwab@linux-m68k.org
GPG Key fingerprint = 58CA 54C7 6D53 942B 1756 01D3 44D5 214B 8276 4ED5
"And now for something completely different."
next prev parent reply other threads:[~2013-08-16 22:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-16 10:43 [PATCH] CET is only one hour ahead of UTC, it even says so in date.c Mattias Andrée
2013-08-16 10:53 ` [PATCH] CET is only one hour ahead of UTC Mattias Andrée
2013-08-16 10:54 ` Mattias Andrée
2013-08-16 10:58 ` Mattias Andrée
2013-08-16 12:54 ` Jeff King
2013-08-16 20:32 ` Andreas Schwab [this message]
2013-08-17 3:52 ` [PATCH v2] CEST is +0200 during April Mattias Andrée
2013-08-17 6:36 ` Aaron Schrab
2013-08-17 6:40 ` Mattias Andrée
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=877gfl1imp.fsf@igel.home \
--to=schwab@linux-m68k.org \
--cc=git@vger.kernel.org \
--cc=maandree@operamail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).