On 3/31/17, Jan Nijtmans wrote:
> 2017-03-31 17:04 GMT+02:00 Richard Hipp:
>> I don't understand the details of this issue, but my instinct would be
>> to use the T card to avoid an incompatibility.
>
> Thanks! Does that mean that the "jn-export" branch can be merged
> to trunk? Then GIT tag comme
2017-03-31 17:04 GMT+02:00 Richard Hipp:
> I don't understand the details of this issue, but my instinct would be
> to use the T card to avoid an incompatibility.
Thanks! Does that mean that the "jn-export" branch can be merged
to trunk? Then GIT tag comments will sync with fossil, both ways.
Reg
I don't understand the details of this issue, but my instinct would be
to use the T card to avoid an incompatibility.
On 3/31/17, Jan Nijtmans wrote:
> 2017-03-30 21:24 GMT+02:00 Richard Hipp:
>> On 3/30/17, Jan Nijtmans wrote:
>>> Ping .Could this be decided for Fossil 2.2? Please?
>>
>
2017-03-30 21:24 GMT+02:00 Richard Hipp:
> On 3/30/17, Jan Nijtmans wrote:
>> Ping .Could this be decided for Fossil 2.2? Please?
>
> libfossil is a non-trivial undertaking. Because of the way Fossil is
> currently architected, libfossil is basically a ground-up rewrite.
Hm. My question
