To fix invalid timezone info in a repo I ran
git filter-branch --env-filter '
GIT_AUTHOR_DATE=`echo ${GIT_AUTHOR_DATE}|sed s/+0000/-0800/`' HEAD
This fixed the invalid entries but the new timezone is -0700
instead of -0800. Is this expected?
git version 1.7.4.rc2
From: Johannes Sixt <hidden> Date: 2016-06-15 22:50:26
Am 1/18/2011 17:43, schrieb Tuncer Ayaz:
To fix invalid timezone info in a repo I ran
git filter-branch --env-filter '
GIT_AUTHOR_DATE=`echo ${GIT_AUTHOR_DATE}|sed s/+0000/-0800/`' HEAD
This fixed the invalid entries but the new timezone is -0700
instead of -0800. Is this expected?
Parse error. You fixed it, but it is not fixed? So what?
What do you mean by "the new timezone is"? Do you mean "...is reported
as"? If so, reported by which tools?
git version 1.7.4.rc2
I tried your command, but the timezone was changed in the expected way.
-- Hannes
On Wed, Jan 19, 2011 at 8:01 AM, Johannes Sixt wrote:
Am 1/18/2011 17:43, schrieb Tuncer Ayaz:
quoted
To fix invalid timezone info in a repo I ran
git filter-branch --env-filter '
GIT_AUTHOR_DATE=`echo ${GIT_AUTHOR_DATE}|sed s/+0000/-0800/`' HEAD
This fixed the invalid entries but the new timezone is -0700
instead of -0800. Is this expected?
Parse error. You fixed it, but it is not fixed? So what?
Fixed because it is not +0000 anymore. Surprised because the new
timezone is -0700 and not -0800.
What do you mean by "the new timezone is"? Do you mean "...is reported
as"? If so, reported by which tools?
git log
git cat-file $REV
quoted
git version 1.7.4.rc2
I tried your command, but the timezone was changed in the expected way.
From: Johannes Sixt <hidden> Date: 2016-06-15 22:50:26
Am 1/19/2011 11:08, schrieb Tuncer Ayaz:
On Wed, Jan 19, 2011 at 8:01 AM, Johannes Sixt wrote:
quoted
Am 1/18/2011 17:43, schrieb Tuncer Ayaz:
quoted
To fix invalid timezone info in a repo I ran
git filter-branch --env-filter '
GIT_AUTHOR_DATE=`echo ${GIT_AUTHOR_DATE}|sed s/+0000/-0800/`' HEAD
This fixed the invalid entries but the new timezone is -0700
instead of -0800. Is this expected?
Parse error. You fixed it, but it is not fixed? So what?
Fixed because it is not +0000 anymore. Surprised because the new
timezone is -0700 and not -0800.
quoted
What do you mean by "the new timezone is"? Do you mean "...is reported
as"? If so, reported by which tools?
git log
git cat-file $REV
$ git filter-branch -f --env-filter 'echo; echo "$GIT_AUTHOR_DATE"; GIT_AUTHOR_DATE=`echo ${GIT_AUTHOR_DATE}|sed s/+0100/-0800/`; echo "$GIT_AUTHOR_DATE"' -- -1
Rewrite 6fb5ec91707a4433628eae5d9d68153ca8b819fe (1/1)
1292311163 +0100
1292311163 -0800
Ref 'refs/heads/master' was rewritten
$ git cat-file commit HEAD
tree 43554f2216bbcfc96385db0641ae212409f26f21
parent 942f54790453970cfffbfedf29e47ac27b9ba995
author Johannes Sixt [off-list ref] 1292311163 -0800
committer Johannes Sixt [off-list ref] 1292311163 +0100
master
*Shrug*
-- Hannes
On Wed, Jan 19, 2011 at 11:32 AM, Johannes Sixt wrote:
Am 1/19/2011 11:08, schrieb Tuncer Ayaz:
quoted
On Wed, Jan 19, 2011 at 8:01 AM, Johannes Sixt wrote:
quoted
Am 1/18/2011 17:43, schrieb Tuncer Ayaz:
quoted
To fix invalid timezone info in a repo I ran
git filter-branch --env-filter '
GIT_AUTHOR_DATE=`echo ${GIT_AUTHOR_DATE}|sed s/+0000/-0800/`' HEAD
This fixed the invalid entries but the new timezone is -0700
instead of -0800. Is this expected?
Parse error. You fixed it, but it is not fixed? So what?
Fixed because it is not +0000 anymore. Surprised because the new
timezone is -0700 and not -0800.
quoted
What do you mean by "the new timezone is"? Do you mean "...is reported
as"? If so, reported by which tools?