On 8/6/18, joerg van den hoff <veedeeh...@gmail.com> wrote: > this is a pure > CLI/ssh scenario.
The ssh transport works by invoking the same HTTP processing engine as is used on a website, just on the far end of an ssh tunnel. It's all the same under the covers. That said, I do remember making some minor changes to the ssh transport as part of the refactoring that is currently taking place. Maybe something broke. Can you bisect back to the last release and figure out where the problem was introduced? That would be a big help. > overall, I really hope that not too much complexity is currently added > to fossil that could lead to a situation where fossil no longer excels > by ease of use and stability/absence of problems or serious bugs as it > has done now for so many years, thankfully. There is a lot of refactoring going on right now, in an effort to avoid introducing unnecessary complexity. -- D. Richard Hipp d...@sqlite.org _______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
