I've retested with: This is fossil version 1.36 [35d43fd98f] 2016-08-27 21:16:29 UTC
and the behavior is still the same. More, on the client side which would like to update from the git -> fossil incremental mirror I see this: changes: None. Already up-to-date WARNING: multiple open leaf check-ins on trunk: (1) 2016-09-01 15:01:45 [40ac6bac70] (2) 2016-09-01 08:45:58 [1831910f11] (3) 2016-08-30 14:56:39 [cd5ce7b43e] (4) 2016-08-28 06:15:32 [91ac797edb] (current) in UI/server I see that there are basically 4 lines of code changes, every line presented probably from changes which I imported incrementally from git. The client code which I try to update above comes from checkout done after first git -> fossil conversion. It seems it completely miss opportunity to update from leafs 1/2/3. My question is: is it possible somehow to connect those open leafs together to form one line of development which is really what's in to fossil imported git repo? Thanks! Karel On Tue, Feb 9, 2016 at 10:32 PM, Karel Gardas <gard...@gmail.com> wrote: > On Tue, Feb 9, 2016 at 10:28 PM, Richard Hipp <d...@sqlite.org> wrote: >> On 2/9/16, Karel Gardas <gard...@gmail.com> wrote: >>> is this a known issue or do I do something completely wrong? >>> >> >> Neither. You are dealing with seldom-used functionality that >> apparently has never been fully debugged. >> > > Thanks for super-fast feedback. May I count with you on pushing this > to fossil bug db? Thanks! _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
