Overview
Artifact ID: | a2b7265dc07d27c06c3947dba04155db49cc1524 |
---|---|
Ticket: | 5927b038735a081b8490990fbff378178c6d7d20 |
Date: | 2011-04-11 11:29:41 |
User: | anonymous |
Artifact Attached: | acf80b30877633b8f8b6e1bd2eb4b5829f8473f6 |
Filename: | mfuf.txt |
Description: | My root message as it was meant to be sent without the posting software combining multiple lines into one. |
Content Appended
I would like timeline to produce output that is machine friendly to scripts that process it. I am trying to automate the building process of my software and I would like to use tags of the form: RELEASE-1.6.10 which can be embedded in the program so that users get a nice human-friendly version number. Timeline has the feature of showing all checkins that descend from current. The intention is to feed this into a script which cna detect if a RELEASE has already been used. The problem is that timeline sometimes splits a tag onto two lines. Here's an example: === 2011-04-10 === 20:44:26 [59a3f097fb] junk (user: davidevans tags: tiger-branch, RELEASE- 1.6.10, jjjj) This makes life very difficult for script writers. Could we please have an option of timeline that produces machine-readable text ? example 2011-04-10T20:46:20 [acdf123456] commit message (user: joe tags: RELEASE-1.6.99 tiger-branch )