OK, thank you.
On 12/04/2017 12:51, Richard Hipp wrote:
> On 4/12/17, Ron Aaron wrote:
>> I know how I can get the latest version; but I am quite concerned that if I
>> do update my system, my users will be unable to sync unless they also go
>> through that process.
>>
>>
>> I don't think it sho
On 4/12/17, Ron Aaron wrote:
> I know how I can get the latest version; but I am quite concerned that if I
> do update my system, my users will be unable to sync unless they also go
> through that process.
>
>
> I don't think it should be the case that I cannot sync to a repo after an
> upgrade.
I know how I can get the latest version; but I am quite concerned
that if I do update my system, my users will be unable to sync
unless they also go through that process.
I don't think it should be the case that I cannot sync to a repo
after an upgrade. W
On 04/11/2017 09:08 PM, Ron Aaron wrote:
My current fossil is "This is fossil version 1.37 [df1205bb3a]
2016-11-07 11:26:26 UTC", not such an old version.
Download binaries or source from here:
https://www.fossil-scm.org/index.html/uv/download.html
This will get you caught up with the sha3 ch
My current fossil is "This is fossil version 1.37 [df1205bb3a]
2016-11-07 11:26:26 UTC", not such an old version.
When I try to update to the latest fossil trunk, I get:
Autosync: https://fossil-scm.org/
Round-trips: 1 Artifacts sent: 0 received: 0
unknown command: [igot]
Rou
5 matches
Mail list logo
