Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Andy Bradford
Thus said Richard Hipp on Sun, 10 Dec 2017 19:20:59 -0500: > Minor correction: the hash algorithm changes was from SHA1 to > SHA3-256. I would call that a major correction! I knew something didn't seem right about what I sent... Thanks, Andy -- TAI64 timestamp: 40005a2df05f

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Richard Hipp
On 12/10/17, Andy Bradford wrote: > artifact IDs have changed from MD5 > hashes to SHA256 hashes Minor correction: the hash algorithm changes was from SHA1 to SHA3-256. SHA1 is still supported, but the Fossil self-hosting repo now uses SHA3 for newer check-ins, so

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Michai Ramakers
On 10 December 2017 at 17:57, Andy Bradford wrote: > Thus said Michai Ramakers on Sun, 10 Dec 2017 16:21:02 +0100: > >> michai@work-lap:/tmp/f/f$ f ver >> This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC > > Since then Fossil has had much development.

[fossil-users] TAB size in displayed content

2017-12-10 Thread Thomas
It seems lots of changes regarding Fossil's web appearance are going on at the moment. I'm not particularly skilled when it comes to CSS but from what I've looked up so far it seems the reason why horizontal tabs in artifacts are 8 characters wide is because { tab-size: 4; } doesn't appear.

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Andy Bradford
Thus said Michai Ramakers on Sun, 10 Dec 2017 16:21:02 +0100: > michai@work-lap:/tmp/f/f$ f ver > This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC Since then Fossil has had much development. In this case, the change that is breaking you is that the artifact IDs have

Re: [fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Michai Ramakers
On 10 December 2017 at 16:15, Michai Ramakers wrote: > > Is it normal that I can't seem to clone the fossil-scm.org repo using > this old version? Apparently I have been living under a rock. I also seem to be unable to open the cloned (using current trunk) fossil-scm.org

Re: [fossil-users] How to revert a wiki page to a specific revision

2017-12-10 Thread Offray Vladimir Luna Cárdenas
Thanks Warren. I will change to embedded documentation for this Fossil repo also. Cheers, Offray On 07/12/17 19:35, Warren Young wrote: > On Dec 7, 2017, at 10:41 AM, Offray Vladimir Luna Cárdenas > wrote: >> I have been looking in the help on revert, but it seems related

[fossil-users] trouble cloning current fossil-scm.org repo with old fossil (2015)

2017-12-10 Thread Michai Ramakers
Hi, I haven't tracked trunk since end of 2015. Is it normal that I can't seem to clone the fossil-scm.org repo using this old version? michai@work-lap:/tmp/fold$ f ver This is fossil version 1.33 [b00e60194e] 2015-08-22 12:42:15 UTC michai@work-lap:/tmp/fold$ f clone https://www.fossil-scm.org/