Any reason for not using one of the established web servers that
actually implement the specs correctly? E.g. with nginx you can either
hook up fossil http via inetd or directly proxying fossil server.
If I understand it correctly fossil uses non-parsed headers in its answers
(runs as a
2011/1/17 Kulcsár Ferenc crusa...@netbsd.hu
If I understand it correctly fossil uses non-parsed headers in its answers
(runs as a non-pased header script).
I don't think so. The webserver on the http://www.fossil-scm.org/ website
does not support non-parsed headers but it supports Fossil
On Mon, Jan 17, 2011 at 09:32:22AM +0100, Kulcsár Ferenc wrote:
Any reason for not using one of the established web servers that
actually implement the specs correctly? E.g. with nginx you can either
hook up fossil http via inetd or directly proxying fossil server.
If I understand it
On 17 January 2011 01:29, Ron Wilson ronw.m...@gmail.com wrote:
On Sun, Jan 16, 2011 at 5:24 AM, David Bovill da...@architex.tv wrote:
Do you mean only in Fossil's file display,
Yes - this is the main need. Simply put you have to be able to move back and
forth between source code and
On Sun, 16 Jan 2011 10:24:16 +, David Bovill wrote:
One think I'm missing in terms of usability is the ability to
intimately link a particular source code file with a wiki page. AFAIK
this is not part of the structure or interface at the moment - so no
wiki-tags for linking to / embedding
5 matches
Mail list logo
