Metzler, Eric wrote:
> I just got around to testing this. Unfortunately, I don't think the fix
> works in my situation.
> All my checkouts directly from a specific branch, tag, or from the trunk
> work fine. This problem seems to be related to the checkouts from a
> subdirectory of a branch, tag or trunk. For example, an outline of our
> structure is as follows:
> If I checkout the trunk folder, the revision graph works fine, but since
> we are checking out dir1, 2, and 3 to different locations, the graph
> does not display properly. Attached is a screenshot of a directory that
> is at rev 379 and should also be showing modifications, but does not
> (revgraph.png). Revgraph1.png is a shot of the revision graph for
> another subdirectory of that library that is at rev 477, but does not
> show it.
> I am using nightly build 17948. Hope this helps.
It did and as a result, it extended the functionality
in r18367. The old code did the following:
* get the latest _commit_ revision
* make / insert node for that path and revision
If you create a copy of e.g. /trunk, the latest commit
revision of its sub-nodes does not change. Therefore,
this revision may date back to long before the copy
was made, it to a point in time where the path in question
didn't exist. -> No node will be highlighted.
* find min & max commit revisions
* find min & max update ("at") revisions
* follow renames etc. when looking up paths
* mark commit revs with thick dotted borders
* mark min update revision with thick dashed border
* mark max update revision with thick solid border
* indicate multiple status by combining border styles
(dash - dot)
There is still a bug in the combining logic. I will commit
the fix as soon as I'm back at the hotel.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2010-01-21 04:26:22 CET