Re: AW: Status update - version 5.2.2, cvs->git conversion, plans

[Daniel J S. <dan...@ie...>]

On 11/17/2017 02:29 AM, Bastian Märkisch wrote:
>>
>> We seem to be talking past each other.
>> I do not care about further tweaks to the tags or branches.
>> Their conversion is sufficiently good.
>>
>> The remaining issue is incorrectly converted timestamp and author
> attribution.
>> I found a script that automates a recipe that is basically
>>
> (snip)
>>
>> However I tried using this recipe to make one change and it failed.
>> The filter-branch step spit out progress updates for about half an hour
>> and then died.   Repository too large or too complicated?
>> Some issue with branch structure that is non-fatal form most purposes but
> trips
>> up this specific operation?
>> Whatever, it doesn't work.
>>
>> The other alternative is to use reposurgeon during, rather than after, the
>> conversion.  Bastian was having problems with that path also.
>>
>> 	Ethan
>>
> 
> What I have been trying to do is to manually add author changes to the Eric
> Raymond's reconvert script.  The example command given was:
>   <es...@th...!2017-11-04T16:44:25> setfield author "Frd J. Foonly
> <fr...@fo...>"
> (which according to the docs probably should instead be
> <2017-11-04T16:44:25! es...@th...> setfield author "Frd J. Foonly
> <fr...@fo...>"
> 
> Unfortunately, such commands do not "find" the entry, not even with the tip
> version of reposurgeon.
> So I am kind of stuck for the moment.

There can't be a space in the search field <2017-11-04T16:44:25! 
es...@th...>  I'm assuming you don't have any in what you are 
searching for.

You are likely running into what I ran into with experimenting with 
tags, the time-zone factor.  You must specify the exact time in the 
search field <>, but often git displays some kind of time zone-adjusted. 
  So I had to do trial and error shifting by 7 hours to put times in 
GMT, e.g., <2013-04-11T20:04:07Z>.  (Note the added Z...search Zulu time 
in Wikipedia:

https://en.wikipedia.org/wiki/Time_zone

)

For example, doing the git log as you suggested, I see a time

2000-10-20T20:01:32+01:00

which would be

2000-10-20T20:01:32Z

I think.  Anyway, I used git times from qgit that didn't have that extra 
UTC offset value so I often had to compute the proper UTC time and 
rarely got it right on the first try.

Dan