you are an advanced user, you know for clear its internal workings and
I somehow too.
You mention the context. What context? I had to ask what was this context after
viewing the c structure defining stash on this list. The context is
not mentioned
in the --help mode and is not even mentioned
On May 12, 2016, at 5:38 PM, Ron W wrote:
>
> On Thu, May 12, 2016 at 5:14 PM, Warren Young wrote:
> Where would it get the user credentials for that? Modifying tickets is not
> allowed for anonymous.
>
> The update would be to the same repo as the
On May 13, 2016, at 10:45 AM, Ron W 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
On Fri, May 13, 2016 at 11:45 AM, Warren Young wrote:
> On May 12, 2016, at 5:38 PM, Ron W wrote:
> > The update would be to the same repo as the commit, so the URL would be "
> http://localhost:8080/tktedit; so credentials would not be needed.
>
>
On Fri, May 13, 2016 at 4:02 PM, Warren Young wrote:
> Again, I don’t see why you’d want to spend a lot of effort expanding TH1
> to support this. That requires every Fossil user to rebuild Fossil with
> TH1 hook support and install the custom hook. This should be built into
On Fri, May 13, 2016 at 12:58 PM, Warren Young wrote:
>
> 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
On May 13, 2016, at 1:16 PM, Ron W wrote:
>
> I did not claim my scheme would work for a remote Fossil server.
The HTTP server provided by “fossil ui” is still “remote” as far as my
questions go.
The point is, the command line fossil client making the ci call probably
7 matches
Mail list logo