On Tue, Jun 7, 2016 at 2:27 AM, Luca Ferrari wrote:
>
> In the meantime I've tried the desperate trick:
>
> % fossil merge --integrate --force aa9521ccd9
>
> but the leaf is still listed on the open ones.
>
As Richard said, it's not a real problem.
I would suggest you
On 6/7/16, Luca Ferrari wrote:
> On Mon, Jun 6, 2016 at 10:59 AM, Richard Hipp wrote:
>> No. Can you make the repo available for analysis?
>>
>
> Sorry, my employer does not grant me to do it. Is there anything I can
> export that can be useful? The repo
On Mon, Jun 6, 2016 at 10:59 AM, Richard Hipp wrote:
> No. Can you make the repo available for analysis?
>
Sorry, my employer does not grant me to do it. Is there anything I can
export that can be useful? The repo is actually 800+MB.
In the meantime I've tried the desperate
On 6/6/16, Luca Ferrari wrote:
> On Tue, May 31, 2016 at 4:28 PM, Luca Ferrari
> wrote:
>> The commit is marked as merged and the branch is shown in the closed
>> list, am I missing something?
>> What could happen if I try to reclose the open leaves?
On Tue, May 31, 2016 at 4:28 PM, Luca Ferrari wrote:
> The commit is marked as merged and the branch is shown in the closed
> list, am I missing something?
> What could happen if I try to reclose the open leaves?
Anyone has an idea of what is fossil telling me?
Just for
On Tue, May 31, 2016 at 2:26 PM, Joerg Sonnenberger wrote:
> On Tue, May 31, 2016 at 01:50:01PM +0200, Luca Ferrari wrote:
>> So the branch 'feature-installazioni' is closed, and is merged.
>> I'm a little confused.
>
> A merge doesn't automatically close a branch, it must be
On Tue, May 31, 2016 at 01:50:01PM +0200, Luca Ferrari wrote:
> So the branch 'feature-installazioni' is closed, and is merged.
> I'm a little confused.
A merge doesn't automatically close a branch, it must be instructed so.
Joerg
___
fossil-users
On Tue, May 31, 2016 at 8:16 AM, Luca Ferrari wrote:
> WARNING: multiple open leaf check-ins on trunk:
> (1) 2016-05-30 15:25:09 [fc75337a99] (current)
> (2) 2015-11-19 14:08:50 [aa9521ccd9]
> (3) 2015-08-26 08:18:19 [c413c4592a]
I've tried to inspect one of the open
On Mon, May 30, 2016 at 6:12 PM, Joerg Sonnenberger wrote:
>> Maybe the LEAF table in the database file is somehow out of sync.
>> Have you tried running "fossil rebuild" to see if that clears the
>> problem?
>
> Or the more light-weight "fossil leaves --recompute" for starters.
On Mon, May 30, 2016 at 11:49:47AM -0400, Richard Hipp wrote:
> On 5/30/16, Luca Ferrari wrote:
> > Hi all,
> > I suspect I did not get right the multiple open leaf warning:
> >
>
> Maybe the LEAF table in the database file is somehow out of sync.
> Have you tried running
On 5/30/16, Luca Ferrari wrote:
> Hi all,
> I suspect I did not get right the multiple open leaf warning:
>
Maybe the LEAF table in the database file is somehow out of sync.
Have you tried running "fossil rebuild" to see if that clears the
problem?
--
D. Richard Hipp
Hi all,
I suspect I did not get right the multiple open leaf warning:
% fossil stat
...
checkout: fc75337a991c9a1156735b1eca3f9cdd0d2ca70f 2016-05-30 15:25:09 UTC
parent: e7c2399f591e36e1ec947dfb7b034b2c02697b4b 2016-05-30 12:37:08 UTC
tags: trunk
...
WARNING: multiple open leaf
12 matches
Mail list logo