On May 13, 2016, at 10:45 AM, Ron W <[email protected]> wrote: > > > Without that cookie, fossil server doesn’t know that fossil client is > > logged in. > > When the Fossil server is started with "fossil ui path/to/repo &”
We aren’t talking about fossil ui. We’re talking about $ f ci -m “closes [12345abc]” Under your scheme, that would run a TH1 commit hook. So: does an HTTP call made from fossil ci send a suitable cookie to tell the remote fossil server on autosync that it is user foo, so it should let it close ticket [12345abc]? _______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
