threads / discuss / 26300

filter-branch --env-filter GIT_AUTHOR_DATE

Subject: filter-branch --env-filter GIT_AUTHOR_DATE

## tl;dr

6 messages between Jan 18, 2011 and Jan 19, 2011.

replies: 5people: 2as markdown or json

Tuncer Ayaz· Jan 18, 2011, 16:43 UTC · lore
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
Johannes Sixt· Jan 19, 2011, 07:01 UTC · re: Tuncer Ayaz · lore

Re: filter-branch --env-filter GIT_AUTHOR_DATE

Am 1/18/2011 17:43, schrieb Tuncer Ayaz:
Show 6 quoted lines
> 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
Tuncer Ayaz· Jan 19, 2011, 10:08 UTC · re: Johannes Sixt · lore

Re: filter-branch --env-filter GIT_AUTHOR_DATE

On Wed, Jan 19, 2011 at 8:01 AM, Johannes Sixt wrote:
Show 9 quoted lines
> 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?

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

>> git version 1.7.4.rc2
>
> I tried your command, but the timezone was changed in the expected way.
How did you check?
Johannes Sixt· Jan 19, 2011, 10:32 UTC · re: Tuncer Ayaz · lore

Re: filter-branch --env-filter GIT_AUTHOR_DATE

Am 1/19/2011 11:08, schrieb Tuncer Ayaz:
Show 19 quoted lines
> On Wed, Jan 19, 2011 at 8:01 AM, Johannes Sixt wrote:
>> 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?
> 
> 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

$ 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 <j.sixt@viscovery.net> 1292311163 -0800 committer Johannes Sixt <j.sixt@viscovery.net> 1292311163 +0100

master
*Shrug*
-- Hannes
Tuncer Ayaz· Jan 19, 2011, 14:30 UTC · re: Johannes Sixt · lore

Re: filter-branch --env-filter GIT_AUTHOR_DATE

On Wed, Jan 19, 2011 at 11:32 AM, Johannes Sixt wrote:
Show 38 quoted lines
> Am 1/19/2011 11:08, schrieb Tuncer Ayaz:
>> On Wed, Jan 19, 2011 at 8:01 AM, Johannes Sixt wrote:
>>> 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?
>>
>> 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
>
> $ 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 <j.sixt@viscovery.net> 1292311163 -0800
> committer Johannes Sixt <j.sixt@viscovery.net> 1292311163 +0100
>
> master
>
> *Shrug*
Cannot reproduce anymore. Works as expected.
Successfully rewrote all GIT_AUTHOR_DATE timezone entries:
  -0700 -> -0800
  -0800 -> +0000
  +0000 -> -0800
git version 1.7.4.rc2.3.g60a2e

← back to recent threads