Guess my photo got blocked -
https://www.sqlite.org/src/timeline?c=2010-09-28+20:26:44 shows the
time-warp but also the tag messages fixing them (which I guess you later
unfixed in the db).

On Mon, Nov 3, 2014 at 5:46 PM, E. Timothy Uy <t...@loqu8.com> wrote:

> Ok, I now see that you intentionally left 2 time-warps in place. It would
> be helpful to make that as a note for exporting to git. It is also
> confusing that the tags are there showing that they were fixed.
>
> On Mon, Nov 3, 2014 at 5:44 PM, E. Timothy Uy <t...@loqu8.com> wrote:
>
>> Dear Richard,
>>
>> It is strange, but if you look at the timeline image I sent (second
>> email), your time-warp tag changes are clearly there but did not stick on
>> objid 35450 and 35460. I just manually did mine on this end (following your
>> same times) and it is now ok, though I feel a bit dirty changing commit
>> times!
>>
>> Leaving the time-warp in place will affect git export. Also, the other
>> barrier that blocks git export of the current sqlite version is that in the
>> fossil export.c, the pid needs to be filtered by type='ci' as one of the
>> parents is type='g' (tag). I have that in some notes in
>> http://www.fossil-scm.org/index.html/tktview?name=4013b0a81a
>>
>>     db_prepare(&q3,
>>       "SELECT pid FROM plink"
>>       " WHERE cid=%d AND isprim"
>>       "   AND pid IN (SELECT objid FROM event WHERE type='ci')",
>>       ckinId
>>     );
>>
>> Respectfully,
>> Tim
>>
>> On Mon, Nov 3, 2014 at 5:37 PM, Richard Hipp <d...@sqlite.org> wrote:
>>
>>> On Mon, Nov 3, 2014 at 8:13 PM, E. Timothy Uy <t...@loqu8.com> wrote:
>>>
>>> > I found some posts in the past describing fixing time-warps using
>>> tags. How
>>> > does this process get initiated? I found two while trying to export to
>>> .git
>>> >
>>>
>>>
>>> The test_timewarps webpage will show them all to you.  Example:
>>>
>>>      http://www.sqlite.org/src/test_timewarps
>>>
>>> In the example above, most of the timewarps have been fixed.  To fix
>>> them,
>>> simple edit check-ins and change their time.
>>>
>>> I intentionally left one timewarp in SQLite unfixed.  See the
>>> https://www.sqlite.org/src/timeline?p=3f30f00a384d23&d=3f30f00a384d235
>>> timeline.  I left this one as a test case for ensuring that Fossil can
>>> display timewarps correctly.
>>>
>>>
>>>
>>>
>>> >
>>> > sqlite> SELECT l.*, ep.mtime, ec.mtime FROM plink l LEFT JOIN event ep
>>> ON
>>> > pid = ep.objid LEFT JOIN event ec ON cid = ec.objid WHERE ep.mtime >
>>> > ec.mtime LIMIT 10;
>>> >
>>> > 35460|35462|1|2455469.26833333|2455469.46484954|2455469.26833333
>>> >
>>> > 35450|35453|1|2455468.35189815|2455468.80332176|2455468.35189815
>>> >
>>> > Respectfully,
>>> >
>>> > Tim
>>> > _______________________________________________
>>> > sqlite-users mailing list
>>> > sqlite-users@sqlite.org
>>> > http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>>> >
>>>
>>>
>>>
>>> --
>>> D. Richard Hipp
>>> d...@sqlite.org
>>> _______________________________________________
>>> sqlite-users mailing list
>>> sqlite-users@sqlite.org
>>> http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
>>>
>>
>>
>
_______________________________________________
sqlite-users mailing list
sqlite-users@sqlite.org
http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users

Reply via email to