Re: Adding merge arrows on Revision Graphs

Wai,

You could create a program that queries SVN for the info (merge info is
stored as properties) and generate the graph yourself. I'd suggest
outputting DOT format and using GraphVis to draw the diagram.

The reason a lot of work is needed is because each new commit gets a full
copy of all past merge info, so is necessary to compare commits and
"subtract" past info to get the commits own info.

Also, is possible for each file and directory to have its own merge
history, so this makes the processing more complex.

The reason SVN stores merge info that way is that is faster for SVN to
determine what has already been merged, therefore, what needs to be merged
when a "svn merge" command is run. Only need to fetch merge info from the
commits being merged, not their ancestors.

On Fri, Apr 7, 2017 at 12:21 PM, Wai <waichak.luk_at_pw.utc.com> wrote:

> Why not tell the user that such an operation would take a really really
> long time? Make an button for the user as an option on the revision graph
> and a warning that it may take hrs.
>
> This will be a very useful feature in meetings and such. One can prepare
> for this over night for say a team meeting.
>
> ------------------------------------------------------
> http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=
> 4061&dsMessageId=3227499
>
> To unsubscribe from this discussion, e-mail: [users-unsubscribe@
> tortoisesvn.tigris.org].
>

------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3227867

To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-04-09 00:05:51 CEST