On 8/9/16, fossil-dev@mailinglists.sqlite.org
<fossil-dev@mailinglists.sqlite.org> wrote:
> On Tue, 22 Dec 2015 18:15:38 -0500
> Richard Hipp <d...@sqlite.org> wrote:
>
>> Anything you can do to help figure this out will be appreciated.
>
> I do not see any news in regard and considering that in a recent time
> I'm doing some small contributions to Github-hosted project(s), I'd
> really like to be able to avoid changing gears in {Fossil, Git} usage,
> so wonder if there is some update on this support?
>
> Is help in doing some research work still required?
>

Getting Fossil to talk to Git *efficiently* is a problem.

The issue is that both Git and Fossil try to exchange information
between client and server in its original delta-ed and compressed
format.  So, essentially, a push or pull operation is only slightly
more complicated than an scp.

In order to Fossil to speak "Git", it would be necessary to insert a
format translator.  Thus as information flowed from Fossil to Git, it
would be necessary to decompress and decode it all, convert it into
the Git format, then recompress and reencode it.  That is likely to be
quite slow in comparison to doing a blind "scp" type operation.

I am still working the problem.  But for the moment I am trying to get
the "unversioned files" feature going.
-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-dev mailing list
fossil-dev@mailinglists.sqlite.org
http://mailinglists.sqlite.org/cgi-bin/mailman/listinfo/fossil-dev

Reply via email to