monotone-devel
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Monotone-devel] git fast-export


From: Felipe Contreras
Subject: Re: [Monotone-devel] git fast-export
Date: Sun, 18 Jan 2009 09:26:20 +0200

On Sun, Jan 18, 2009 at 1:18 AM, Paul Aurich <address@hidden> wrote:
> And Felipe Contreras spake on 01/17/2009 02:52 PM, saying:
>> I ran my comparison script, but unfortunately the first revision has a
>> missmatch:
>>
>> yours:
>> author Tailor Script <address@hidden> 953780991 +0000
>>
>> mine:
>> author Tailor Script <address@hidden> 953773791 +0200
>>
>> Which suggest that your script is not handling the timezone correctly
>> (not sure about that).
>
> No, his script is handling it properly (based solely on this example).
>
> Monotone uses UTC internally and git does some crazy wacky things with
> timezones (in short, the timezone shown is /just/ for prettifying the date;
> the timestamp by itself *must* be the time of the commit in UTC). See
> https://kerneltrap.org/mailarchive/git/2007/2/6/237902
>
>  $ mtn automate certs d137c7046bae7e4a0144fee82bfce8061f61e3b3 | grep date
> -A 1
>       name "date"
>      value "2000-03-23T03:09:51"
>
>  $ date -d "2000-03-23 03:09:51" -u
>  Thu Mar 23 03:09:51 UTC 2000
>  $ date -d "2000-03-23 03:09:51" -u  +"%s"
>  953780991

True. Then the issue is with my script (ruby date parsing).

It looks like I would have to re-generate my repo clone (yay for one
whole day of conversion) for the comparison.

Before I do that, can we agree on a format for unknown committers?

-- 
Felipe Contreras




reply via email to

[Prev in Thread] Current Thread [Next in Thread]