On 04/07/2018 16:42, jungle Boogie wrote:
On 12:42AM, Wed, Jul 4, 2018 Nicola
> Maybe, the sentence above could be complemented with an example of how
> to do that and how *not* to do it (e.g., explaining what the effect of
> adding a 'trunk' tag to a random check-in is and why it should not
On Thu, Jul 5, 2018 at 5:38 PM Dingyuan Wang wrote:
> Hi,
>
> The following test:
>
> tclsh test/tester.tcl fossil json
>
> fails with:
>
> [...]
> /home/gumble/dev/fossil/fossil json --json-input anon-1
> ERROR: child killed: segmentation violation
>
https://www.fossil-scm.org/index.html/info
On Thu, Jul 5, 2018 at 5:38 PM Dingyuan Wang wrote:
> The following test:
>
> tclsh test/tester.tcl fossil json
>
> fails with:
>
i believe the fix is simply:
[stephan@host:~/fossil/fossil]$ f diff
Index: src/cgi.c
==
--- src/cgi
Hi,
The following test:
tclsh test/tester.tcl fossil json
fails with:
[...]
/home/gumble/dev/fossil/fossil json --json-input anon-1
ERROR: child killed: segmentation violation
JSON ERROR: unexpected token ":" at position 1; expecting VALUE
test json-login-a-env-validJSON FAILED!
test test-fra
Maybe this is a misconfiguration. The www and www3 repositories work fine:
> $ fossil clone https://www.sqlite.org/cgi/src wwwsqlite.fossil
> Round-trips: 10 Artifacts sent: 0 received: 78047
> Clone done, sent: 2667 received: 50594812 ip: 2.0.1.187
> Rebuilding repository meta-data...
> 10
Sure, a name like /wiki/a/b could be interpreted as /wiki?name=a/b, but it
would still break relative paths. It's not enough for Fossil to understand
that the / in a/b isn't a path separator; the browser would need to
understand that as well. Linking to (c) would either go to /wiki/a/c or /c,
but n
On Wed, Jul 4, 2018 at 11:37 PM Stephan Beal wrote:
> i don't _think_ that you can use %2f in a path component and have it apply
> different semantics than a slash. How would software know to differentiate
> between the two? That would be similar to expecting a local file name of
> a\/b to work.
On Jul 4, 2018, at 9:50 AM, Dewey Hylton wrote:
>
> The solution ended up being much less messy than I anticipated
Yes; while Fossil will let you create awful messes, this is mitigated by
several design choices:
1. It’s really hard to make Fossil actually lose data. It can be done, but it
ta
8 matches
Mail list logo
