Files
jami-daemon/src
Sébastien Blin b80ce5103d conversationrepository: avoid recursive merge
There is no need as we always merge two branches so we can avoid
a lot of recursive operations. Moreover, this seems to cause some
weird locks

To be honest I'm not sure about the usage of this argument, doc is
still a bit unclear:

    Maximum number of times to merge common ancestors to build a
    virtual merge base when faced with criss-cross merges.
    When this limit is reached, the next ancestor will simply be used
    instead of attempting to merge it. The default is unlimited.

GitLab: #871
Change-Id: I9c22208626e7f6ff489e91b72a580238a6137499
2023-07-19 15:02:11 -04:00
..
2023-07-17 23:13:31 -04:00
2023-07-13 17:23:24 -03:00
2023-04-26 13:01:08 -04:00
2023-02-06 01:46:45 -05:00
2023-04-13 09:16:19 -04:00
2023-06-20 14:36:37 -04:00
2023-03-14 15:49:31 -04:00
2023-06-05 16:28:50 -04:00
2023-06-28 11:27:35 -04:00
2023-04-26 14:39:33 -04:00
2023-07-13 17:23:24 -03:00
2023-06-20 14:36:37 -04:00
2023-06-09 23:54:57 -04:00
2023-06-02 14:41:06 -04:00
2023-04-26 13:01:08 -04:00
2023-04-26 13:01:08 -04:00
2023-02-06 01:46:45 -05:00
2023-02-06 01:46:45 -05:00
2023-02-06 01:46:45 -05:00
2023-02-06 01:46:45 -05:00
2021-08-12 19:08:45 -04:00
2021-08-12 19:08:45 -04:00