Skip to content

A* add a fossil event/technote point in time message

Fossil events are used to record events at a particular point in time such as:

  • Milestones
  • Blog Entries
  • Process Checkpoints
  • News Articles
  • Announcements
  • Emails

These can be searched and checked using the When search.

The final trick is that the a-event-log component exists the event is also add there so you end up with all events in a-event-log which serves as a diary/changelog for all the components you are working on.

Of course these are all distributed and are synchronised by the normal fossil mechanisms.

% a-event release v1.01
Updated A for B and C.

The first word in the event message is used to select the color the note based on:

array set colors {
release* blue
review* green
accept* gold
warn*|failed* red
* white
}

Open the fossil ui and use the timeline to search.

Some operations in a-make/a-make.mk may create events automatically, e.g. release targets.

  1. Why aren’t commits used? well you need to commit something, create the system and test it. Then you say its passed the tests.
  2. Anything else