On Sat, Jan 3, 2015 at 11:29 PM, Kelly Dean <[email protected]> wrote:
> Does Fossil give any warning if you receive a new ticket update with a > timestamp preceding an update that you yourself created and with a > conflicting J-card? Then #2 would notice #1's update, even though nobody > else would. This won't help if #2 dies too, but it's better than nothing. > This is a good point. As Stephan pointed out, time stamps are not reliable. What might work would be for ticket change artifacts to include a P-card to specify the predecessor artifact. Manifest and Wiki artifacts use this card. If ticket change artifacts also use the P-card, it would be possible to if a given one had sibling artifacts. Currently, the only built-in way Fossil provides to "search" for sibling artifacts is the time line. It would be possible to automate this search using SQL.
_______________________________________________ fossil-users mailing list [email protected] http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
