[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Revision graph revisited

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: 2006-02-07 12:48:55 CET

On 2/7/06, Hans-Emil Skogh <Hans-Emil.Skogh@tritech.se> wrote:

> Let me try to explain my thoughts about the revision graph once more but
> in a slightly more pragmatic way.
> To implement my suggestion, the only thing that would have to be
> modified is the columns of the graph and when to create them. The
> modification would be done in the following way:
> Firstly each column must be able to have a string path and a boolean
> "tag"-state associated with it.
> Column assignment for a item is done in the following way:
> If a copy is made, the copy destination is checked for later
> modifications.
> - If it has modifications it will be added to a column named after the
> destination file's path and with the "tag"-state set to false. If no
> such column exists, one is created.
> - If no modifications are made it will be added to a column named after
> the source file's path, but with the "tag"-state set to true. If no such
> column exists, one is created.

You mean you would show all tags in the same column as e.g. the trunk?
(Assuming the tags aren't modified later at all).

> I have admittedly not looked at the RevGraph-source, and maybe this
> would not be as easy to implement as I might think, but I do think that
> it would add a great value to the Revision Graph.

It won't be easy, but not impossible. So don't expect this feature to
be implemented soon.


  oo  // \\      "De Chelonian Mobile"
 (_,\/ \_/ \     TortoiseSVN
   \ \_/_\_/>    The coolest Interface to (Sub)Version Control
   /_/   \_\     http://tortoisesvn.tigris.org
To unsubscribe, e-mail: dev-unsubscribe@tortoisesvn.tigris.org
For additional commands, e-mail: dev-help@tortoisesvn.tigris.org
Received on Tue Feb 7 12:49:08 2006

This is an archived mail posted to the TortoiseSVN Dev mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.