4 ms·
Hey, are you a fossil dev? I haven't used nor looked at fossil in maybe 5 years, but had a couple of questions. Does fossil now have any kind of email support
by Frondo 7y ago
Hey, are you a fossil dev?
I haven't used nor looked at fossil in maybe 5 years, but had a couple of questions.
Does fossil now have any kind of email support built in to the ticket manager? I remember when I tried to use fossil for actual production use, there was no way to trigger emails sent when, e.g. tickets were submitted, and one of the devs said to just write a script to monitor the fossil rss feed and send the appropriate email, which seemed like a baroque and fragile (and time-consuming) solution.
And is any more of the command-line behavior configurable (like the mv/rm behavior -- affecting the file on disk as well as the repository, or just marking the file as (re)moved in the repository)?
- wyoung2 7y ago> Hey, are you a fossil dev? I have commit access, yes, but mainly I work on the docs. > Does fossil now have any kind of email support built in to the ticket manager? Yes. It was added in support of the forum feature last year, but it also applies to several other event types: https://fossil-scm.org/fossil/doc/trunk/www/alerts.md https://fossil-scm.org/fossil/doc/trunk/www/alerts.md > one of the devs said to just write a script to monitor the fossil rss feed Probably me. :) > seemed like a baroque and fragile (and time-consuming) solution. A dozen lines of Perl; easy-peasy. That and a pile of CPAN modules, but that's easily fetched with `cpanm`. > the mv/rm behavior -- affecting the file on disk as well as the repository The default you're referring to was changed a few years ago: the old `--hard` option is now the default.