Richard wrote: > This is complicated by the fact that Fossil distributed and supports > disconnected operation. So the machine on which a ticket change occurs > might be off-network or might not have out-going email capabilities. > Furthermore, depending on how the privileges are set up, email addresses > might not be distributed with the tickets, since there can be privacy issues > with passing email addresses around. (So, for example, if you clone the > Fossil repository as "anonymous", you'll get all the tickets, but the email > addresses contained in the tickets are obscured and unusable - thus > preventing a spammer from cloning a Fossil repository as a source of new > valid email addresses for their spam lists.) But if the email address is > unknown to the machine that is doing the ticket change, how can an email be > sent? > > The best work-around we have is to use the RSS feed from Fossil to relay > ticket changes to your email. > > > -- > D. Richard hippd...@sqlite.org > > How do we use the RSS feed t get just the tickets and relay them through email? More details appreciated.
If we have a configuration option to enable or disable sending emails, then the user could select that. In addition, fossil can check to see if the email addresses are usable and then notify. A notification from the bug tracking system would be a great addition to fossil. Thanks, Prit
_______________________________________________ fossil-users mailing list fossil-users@lists.fossil-scm.org http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
