From: Christoph Miebach <christoph.miebach@web.de>
To: Junio C Hamano <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: Localization: Timestamps get wrong if using different locales
Date: Sat, 11 Aug 2012 18:22:35 +0200 [thread overview]
Message-ID: <502686CB.1070703@web.de> (raw)
In-Reply-To: <7vmx292hi8.fsf@alter.siamese.dyndns.org>
[-- Attachment #1: Type: text/plain, Size: 2078 bytes --]
Hello!
What I am doing is:
invoking a bash script that does the
git add ${i##$TXPATH/}/strings.xml
git commit --author="$AUTHOR" ${i##$TXPATH\/}/strings.xml -m "l10n:
$LNAME update"
after a user confirmation.
IIUC setting LANGUAGE=en at the top of this script _did_ help.
So I run everything with german locale for reproducing this.
On 05.08.2012 22:47, Junio C Hamano wrote:
> Christoph Miebach <christoph.miebach@web.de> writes:
>
>> Running this commands locally (german locale) lead to some wrong dates
>> for the patches upstream.
>>
>> git format-patch -o patches origin
>
> What does "git show -s --pretty=fuller HEAD" give you at this point?
> This is to check what kind of timestamps are stored in the original
> commit objects.
See pretty_fuller.txt
> And what does "grep '^Date: ' patches/0001-*" show you at this point?
> This is to see if the problem is at the "format-patch" step.
See date_grep.txt
>> git send-email --compose --no-chain-reply-to --to some@address.com
>> --suppress-cc=author patches/0001-l10n-Turkish-update.patch
>
> And what does "grep '^Date: '" for the message that is received by
> recipients show at this step? They cannot be
>
>>
>>
>> The local
>> Date: Sat, 4 Aug 2012
>> became
>> Wed, 8 Dec 2004
>
> as these two do not even have times and zones. It should read
> something like
>
> Date: Sun, 05 Aug 2012 13:39:12 -0700
>
> or something.
It was a complete line. I just did not copy all of it, for I thought I
already pointed out the problem.
The recipient uses en_CA.UTF-8 and guesses:
Date: 12-08-05 06:10 PM
it is Y-M-D, but git thinks it's M-Y-D
> Also "Date" on which message do you see your problem with? The one
> that is created with --compose? Or the one that was originally
> produced by format-patch and then sent? Or both?
git log should show the translators name ($AUTHOR in the git commit line)
Sorry for the late (and probably still incomplete) reply. I can provide
a complete example or send a patch to a dummy project if you prefer some
time next week, I hope.
Regards
Christoph
[-- Attachment #2: pretty_fuller.txt --]
[-- Type: text/plain, Size: 271 bytes --]
commit b6f59b4a61f1bd203bb0d449dabac7b16351e2e1
Author: Christoph Miebach <christoph.miebach@web.de>
AuthorDate: Mon Aug 6 00:07:54 2012 +0200
Commit: Christoph Miebach <christoph.miebach@web.de>
CommitDate: Mon Aug 6 00:07:54 2012 +0200
l10n: German update
[-- Attachment #3: date_grep.txt --]
[-- Type: text/plain, Size: 37 bytes --]
Date: Mon, 6 Aug 2012 00:07:54 +0200
prev parent reply other threads:[~2012-08-11 16:23 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-05 9:08 Localization: Timestamps get wrong if using different locales Christoph Miebach
2012-08-05 20:47 ` Junio C Hamano
2012-08-11 16:22 ` Christoph Miebach [this message]
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=502686CB.1070703@web.de \
--to=christoph.miebach@web.de \
--cc=git@vger.kernel.org \
--cc=gitster@pobox.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).