A fossil commit with a comment such as the following,

---
Note that couchdb document field names are now contained in priv/project.conf file. The strings within the <<>> are the names which should be used in html documents, e.g. <<"_id">> or <<"iata_code">> and the name to POST from a form would be "_id" or "iata_code" respectively.
---

will break my RSS reader when I read timeline.rss ; though I use liferea on GNU/Linux, I believe (though do not know) that illegal XML is being presented by timeline.rss by not escaping or encoding html tags and characters.  For the above comment, liferea says that <<>> is an invalid element name.  I can easily cause breakage by simply adding a commit comment such as

---
bugfix, added the opening &lt;h1&gt; tag in widget.html
---

in which case the RSS reader complains about an open tag with no closing tag.  I then have to wait 20 new commits for the "bad" comment to roll out of the timeline.rss data before I can again read the fossil feed in my RSS reader.

NOTE that I wrote the above tag using encoded less than and greater than signs so that I could create this bug report.  I cannot expect my fossil users (nor myself) to remember to write out ampersand g t ; etc. whenver an html tag is referenced in a commit comment.

Click edit for this report to see the actual text to which I am referring regarding "encoded less than and greater than signs".

My feature request is that timeline.rss present valid parseable XML atom or RSS data.