...
Maybe none at all. The graphic representation of the timeline in the web
interface is really awesome, especially the explicit handling of
branching/merging.
...
one more (cosmetic) item for the wishlist: I would find it really helpful
if the branch/merge information could (optionally or by default)
be integrated as "ascii art" into the `timeline' output. for
illustration, I've converted one of my `fossil' repos to `hg'. with
`hg log -g' (`g' for graphics) I get, e.g., this snippet in the log output:
8<---------------------------------------------------------
o changeset: 45:6afe8c12328f
|\ parent: 41:452701aaa7ca
| | parent: 44:6016c35bcd87
| | user: doe <doe>
| | date: Mon Nov 19 21:22:55 2012 +0000
| | summary: merged revised `theory' section back to trunk.
| |
| o changeset: 44:6016c35bcd87
| | bookmark: sinh
| | user: vdoe <doe>
| | date: Mon Nov 19 21:14:37 2012 +0000
| | summary: mostly finished revision of `theory' section.
| |
| o changeset: 43:fbabab3870b8
| | user: doe <doe>
| | date: Mon Nov 19 16:47:44 2012 +0000
| | summary: tentative overhaul of `theory' section.
| |
o | changeset: 41:452701aaa7ca
|/ user: doe <doe>
| date: Mon Nov 19 16:54:44 2012 +0000
| summary: just a note.
|
o changeset: 40:314da8440e0a
| user: doe <doe>
| date: Fri Nov 16 23:12:19 2012 +0000
| summary: some incremental edits.
8<---------------------------------------------------------
compare this to the corresponding fraction of the `fossil -timeline'
output:
8<---------------------------------------------------------
22:22:55 [217921b304] *MERGE* merged revised `theory' section back to
trunk.
(user: doe tags: trunk)
22:14:37 [71fc7ffa18] mostly finished revision of `theory' section. (user:
doe
tags: sinh)
17:54:44 [a346c75dd2] just a note. (user: doe tags: trunk)
17:47:44 [1a58c5ec33] tentative overhaul of `theory' section. (user: doe
tags:
sinh)
17:46:05 [c4e2b9991d] Create new branch named "sinh" (user: doe tags: sinh)
=== 2012-11-17 ===
00:12:19 [040c7f61a9] *BRANCH* some incremental edits. (user: doe tags:
trunk)
8<---------------------------------------------------------
which is more difficult to translate into the correct mental picture of
the revision tree I'd say.
regarding the intial question: if (if...) the timeline output could
optionally be forced to put each commit message on a single line it
would be very easy (and not that much more difficult with the current
layout) to write a small shell (sed, awk, python, perl ...) script to
extract the messages from the output to generate the desired
changelog, right?
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users
