Provide maximally useful log output.
Registered by
Robert Collins
Per-file log output appears confusing or suboptimal at the moment. The correct output needs to be defined. This needs to consider things like how to render merged revisions that changed the file - whether their visual indent should be preserved, should revisions that merged them be included to allow the depth to step by 1 only ? etc.
Log also fails for non mainline revisions.
And the interface is incomplete, in that some types of formatters (xml) can not be generated with the current api.
Blueprint information
- Status:
- Not started
- Approver:
- Martin Pool
- Priority:
- Medium
- Drafter:
- Martin Pool
- Direction:
- Needs approval
- Assignee:
- None
- Definition:
- New
- Series goal:
- Accepted for trunk
- Implementation:
-
Not started
- Milestone target:
- None
- Started by
- Completed by
Related branches
Sprints
Whiteboard
Open project 10-27-07 trl
(?)
Work Items
Dependency tree

* Blueprints in grey have been implemented.