Thus said Michai Ramakers on Tue, 22 Jul 2014 17:58:24 +0200:
> I don't / didn't use branches other than trunk (which still breaks,
> using your example - good).
Yes, this should work with trunk as long as there are no commits that
follow the one which caused the exclusion of artifacts from
On 22 July 2014 17:29, Andy Bradford wrote:
> Thus said Michai Ramakers on Tue, 22 Jul 2014 12:35:03 +0200:
>
>> I can't seem to reproduce what you describe - either that, or I'm
>> missing the point (did you mean 'merge' as in 'fossil merge'?). I'm
>> assuming you left out 'fossil add'
Thus said Michai Ramakers on Tue, 22 Jul 2014 12:35:03 +0200:
> I can't seem to reproduce what you describe - either that, or I'm
> missing the point (did you mean 'merge' as in 'fossil merge'?). I'm
> assuming you left out 'fossil add' (or 'addremove') twice in your
> example.
Yes,
Thus said Stephan Beal on Tue, 22 Jul 2014 11:36:56 +0200:
> Only one: Keep it up! That was impressive investigatory work! It seems
> to me that you've discovered that fossil does indeed (unintentionally)
> support a form of branch-specific sync ;).
Yes, it's a feature, all those who want bra
On 22 July 2014 10:27, Andy Bradford wrote:
> Thus said "Andy Bradford" on 12 Jul 2014 13:36:58 -0600:
>
>> 2) The artifact rid was in the unclustered table, but when
>> create_cluster() ran it prematurely removed it from the table.
>
> I have been able to successfully reproduce/cau
On Tue, Jul 22, 2014 at 10:27 AM, Andy Bradford
wrote:
> Suggestions?
>
Only one: Keep it up! That was impressive investigatory work! It seems to
me that you've discovered that fossil does indeed (unintentionally) support
a form of branch-specific sync ;).
--
- stephan beal
http://wanderi
Thus said "Andy Bradford" on 12 Jul 2014 13:36:58 -0600:
> 2) The artifact rid was in the unclustered table, but when
> create_cluster() ran it prematurely removed it from the table.
I have been able to successfully reproduce/cause this. When a large
number of artifacts are bein
On 12 July 2014 21:36, Andy Bradford wrote:
>
> I've been trying to investigate the problem that has been reported over
> time and so far I haven't been able to reproduce it or come to any
> conclusive decision regarding what might be the cause. When (in Fossil
> versions) did this proble
Hello,
I've been trying to investigate the problem that has been reported over
time and so far I haven't been able to reproduce it or come to any
conclusive decision regarding what might be the cause. When (in Fossil
versions) did this problem first get noticed or start happening?
Thanks
9 matches
Mail list logo
