On 13 May 2016, at 18:58 , Warren Young wrote:
> We aren’t talking about fossil ui. We’re talking about
>
> $ f ci -m “closes [12345abc]”
+1
___
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mail
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
> the core of Fossi
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 didn’t
keep the cookie
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 tell the remote foss
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 “closes [12345abc]”
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.
>
> Credential lookup is cookie-based. If I make
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 commit, so the URL would be
> "http://local
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 commit, so the URL would be "
http://localhost:8080/tktedit"; so credentials would not be nee
On May 12, 2016, at 2:07 PM, Ron W wrote:
>
> On Wed, May 11, 2016 at 7:29 PM, Warren Young wrote:
> On May 11, 2016, at 3:57 PM, Marko Käning wrote:
> >
> > An auto-closing of tickets if the commit comment contains stg like "closed
> > [TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fi
On Wed, May 11, 2016 at 7:29 PM, Warren Young wrote:
> On May 11, 2016, at 3:57 PM, Marko Käning
> wrote:
> >
> > An auto-closing of tickets if the commit comment contains stg like
> "closed [TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes
> [TICKETID]", would be nice.
>
> Agreed. T
On May 11, 2016, at 3:57 PM, Marko Käning wrote:
>
> An auto-closing of tickets if the commit comment contains stg like "closed
> [TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes [TICKETID]",
> would be nice.
Agreed. The only problem is the perennial one: Someone has to do it. Ar
An auto-closing of tickets if the commit comment contains stg like "closed
[TICKETID]", "closes [TICKETID]", "fixed [TICKETID]", "fixes [TICKETID]", would
be nice.
This is possible to set up in Trac for instance...
___
fossil-users mailing list
fossil-
12 matches
Mail list logo