Re: Revision graph documentation

"Simon Large" <simon.tortoisesvn@googlemail.com> wrote:

> What does the 'group branches together' feature do? Is this the same
> as what was previously called 'arrange by path'? If so the effect
> seems to be reversed in that paths seem more grouped when the option
> is deselected.

No, this is different from the former 'arrange by path' feature.

The default behavior (grouping off) will use one row per revision
and all rows ar sorted strictly by revision. As a result, long-living
branches occupy a whole column for only a few changes and make the
graph become very broad.

Besides the questionable wording, this mode groups changes by branch.
I.e. there is no global revision ordering: Consecutive revisions on
a branch will be shown in (often) consecutive lines. Sub-branches,
however, are arranged in a way that later branches will be shown
"on top" of older branches to keep the graph slim.

As a result, a given row may contain changes from different revisions.
Revision order is only maintained within a column and there only for
the same branch.

> There is an icon for oldest on top and a view menu entry for newest on
> top. The view menu is wrong - when newest is checked the top item is
> the oldest.

Yes, the menu entry is wrong. I will fix that.

> When 'show all revisions' is selected, the HEAD points are no longer
> shown in an ellipse.

Hm. I think I will change that, too.

> How does the 'Fold tags' option work? Does it rely on having /tags/ in
the path?

Yes, it currently relies on the 'tags' string. Maybe, the string can
be made user-defined before feature freeze.

Fold tags will remove all non-changing branches that it considers tags
and list them in the tooltip of the respective last change, instead.
This greately simplifies the graph for single, infrequently changing
documents.

Hopefully, I can extend that feature to non-chaning branches and
renamed / removed branches and tags before feature freeze.

-- Stefan^2.
Received on Tue Sep 11 14:15:10 2007