Hi,
I'd like to know where we are in the topic of hooks. Their lack is one of the
major setbacks of using Fossil. The last time I've noticed a discussion on
their topic it was said, that it's blocked by inability to start background
processes on Windows. Now there is a way to run Fossil itself
On Sat, Sep 10, 2011 at 10:32 AM, Remigiusz Modrzejewski l...@maxnet.org.pl
wrote:
Hi,
I'd like to know where we are in the topic of hooks. Their lack is one of
the major setbacks of using Fossil. The last time I've noticed a discussion
on their topic it was said, that it's blocked by
On Fri, Sep 9, 2011 at 2:46 PM, Martin S. Weber martin.we...@nist.gov wrote:
... and c) a separation of concerns (you, fossil library, take care of
the fossil stuff, I take care of invoking hooks, presenting ...
I think that invoking hooks would be an intermediary between the
client and a pure
On Sep 10, 2011, at 7:53 PM, Richard Hipp wrote:
(3) Use the FTS4 full-text search engine of SQLite to implement full-text
search over the entire repository history.
Ha, that was the next thing I was going to ask ;)
But unfortunately I'm unable to contribute any programming time this month
On Sat, Sep 10, 2011 at 1:53 PM, Richard Hipp d...@sqlite.org wrote:
The hook mechanism should include a delay. This is because client-to-server
push operations can occur in multiple stateless steps, and we really want to
wait and run the hooks after all steps of the push operation are
(Via the command line interface...)
The 'timeline' command can take a -R argument to specify a repository.
It reports a set of information (time, user, check-in id, comment,
etc.), but I do not see it reporting the parent(s) of a check-in
The 'info' command can take an object (for example, a
On Thu, Sep 8, 2011 at 4:08 PM, Ingo Koch ingo.k...@gmx.de wrote:
Take a look at
http://arnebachmann.pytalhost.de/pdf/integrated-version-control-with-fossil-scm.pdf
Good presentation.
I noted it said that configuration is not shared. Actually, it is
possible to share configuration between
On Sat, 10 Sep 2011, Richard Hipp wrote:
The hook mechanism should include a delay. This is because client-to-server
push operations can occur in multiple stateless steps, and we really want to
wait and
run the hooks after all steps of the push operation are complete. So, for example,
On Sat, Sep 10, 2011 at 7:53 PM, Richard Hipp d...@sqlite.org wrote:
(1) Making Fossil more RESTful, and adding JSON replies. Stephan Beal is
already working on this, but I'm sure he'd like to have collaborators.
+1 on that second part :). i made fairly good progress on this on
On Sat, Sep 10, 2011 at 4:49 PM, Gé Weijers g...@weijers.org wrote:
I don't like timers like that, a single server may have clients on fast...
It's been a while since I looked at the protocol specs, but the client
usually maintains (implicit) state in this type of protocol, and could very
On Sun, Sep 11, 2011 at 12:26 AM, Ron Wilson ronw.m...@gmail.com wrote:
In term so f invoking the post hook, I think a timer would be needed.
That can't work in CGI mode, though, only in server mode and only if you
don't kill the server after committing. :/
One of the big hurdles in
On Sun, Sep 11, 2011 at 12:54 AM, Stephan Beal sgb...@googlemail.comwrote:
One of the big hurdles in implementing triggers, i think, has been platform
portability.
s/triggers/hooks/g
--
- stephan beal
http://wanderinghorse.net/home/stephan/
Hi Stephan,
I love JSON web services, and I really like the idea you've presented. I've
often wished I could display Fossil ticket reports in a more flexible way, and
the changes you propose would give me that. I look forward to seeing this
progress.
In my experience writing both JSON web
On Sun, Sep 11, 2011 at 4:19 AM, Clark Christensen cdcmi...@yahoo.comwrote:
In my experience writing both JSON web services (in Perl), and the
consumers of those services, sometimes you can get output that contains not
only a JSON string, but stray newlines or other (debugging?) output. I'm
This question is primarily aimed at Richard, but anyone who's got some
insight or opinions is of course free to chime in...
As i understand it, the primary intention behind requiring the anonymous
user login is to keep spiders from crawling the whole repo history, and the
distinction between the
15 matches
Mail list logo
