Ticket Hash: | 5927b038735a081b8490990fbff378178c6d7d20 | |||
Title: | Make timeline machine readable | |||
Status: | Closed | Type: | Feature_Request | |
Severity: | Minor | Priority: | ||
Subsystem: | Resolution: | Duplicate | ||
Last Modified: | 2013-08-17 19:32:52 | |||
Version Found In: | bc427ad727 | |||
Description: | ||||
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 ) anonymous added on 2011-04-11 10:45:51 UTC: Believe me, fossil really does split RELEASE-1.6.10 into RELEASE- and 1.6.10 | ||||
User Comments: | ||||
nobody added on 2013-03-19 12:05:12:
This seems to be a duplicate of Feature Request [e167be3b92].
stephan added on 2013-08-17 19:32:52: Closing as dupe of [e167be3b92].
|
Attachments:
- mfuf.txt [download] added by anonymous on 2011-04-11 11:29:41. [details]