Maybe also run "fossil rebuild".  And/or "fossil test-integrity".
Please report any findings.

On 7/20/16, sky5w...@gmail.com <sky5w...@gmail.com> wrote:
> ​Thanks for checking. I am confident we have the tip after merging from
> multiple user commits. But, it is certainly confusing to confirm this
> visually.
>
> http://www.fossil-scm.org/index.html/info/a78e51185326b91f
> Edited Comment: Partially revert [f73411025e8ebec7]
> <http://www.fossil-scm.org/index.html/info/f73411025e8ebec7>. This fixes a
> problem that when closing a fork by just doing "fossil merge" and additonal
> arrow going up is displayed. Probably not the right fix. Remark: reverting
> more than necessary. Already fixed on trunk.
>
> http://www.fossil-scm.org/index.html/info/4cae5c94ea2241b3
> Comment: (cherry-pick) Fix a timeline bug, showing an unintended arrow when
> closing a fork.
>
> Do these commits imply similar errors and fixed on trunk?
>
> I will try compiling the latest fossil code and do a rebuild and report
> back...
>
>
> Thanks for Fossil!
>
> On Wed, Jul 20, 2016 at 8:48 PM, Richard Hipp <d...@sqlite.org> wrote:
>
>> It is difficult to say if this is a bug or a weird repo.  I'd need
>> access to the repo to tell.
>>
>> On 7/20/16, sky5w...@gmail.com <sky5w...@gmail.com> wrote:
>> > I've noticed weird multi-line timelines with v1.35.
>> > Is this a bug or is it the skin run amok?
>> > This repo has only trunk and 1 very old branch.
>> >
>> >
>> https://www.reddit.com/r/fossil/comments/4tti7k/fossil_v1353aa86af6aa_is_this_multiline_timeline/
>> >
>> > Thanks for Fossil!
>> >
>>
>>
>> --
>> D. Richard Hipp
>> d...@sqlite.org
>> _______________________________________________
>> fossil-users mailing list
>> fossil-users@lists.fossil-scm.org
>> http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
>>
>


-- 
D. Richard Hipp
d...@sqlite.org
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to