Hans-Emil Skogh wrote:
>> So, I've implemented a first draft of this. But now I've got a
>> little problem:
>> if each url get's its own column in the graph, it will look *really*
>> awful for e.g. the /tags/ folder. Think about it: each tag will get
>> own column.
>> Do you have a suggestion on how to prevent this or make the graph
>> look nicer?
> When the column (where it should be placed) is chosen for an item, there
> has to be a decision made if that item is a "tag" or not. A "tag" is
> here defined by an item that has no modifications later on. (Copies and
> deletes are not counted as modifications.)
> Each column must be able to have a string path and a Boolean "tag"-state
> associated with it.
> If the item is a "tag", it should end up in a column dedicated for tags
> that originate from the same source path as the item.
[snip Confusing example start]
> The point being:
> "Tags" should be placed in a column named after the source path (of the
> copy operation) and with a "tags"-flag set. (In the confusing example
> illustrated appended to the column name.)
> Non-"tags" should be placed in a column named after the item's own path
> with the "tags"-flag unset.
> Maybe I'm complicating the description... If you still feel uncertain
> about how to go about I'll try to make an illustration.
Good idea, good description, but I don't think the method for
identifying tags will work.
1. New branches are indistinguishable from tags.
2. In TSVN at least, there are further commits to tags to update the
language packs after the code is released.
Another way to do it would be to assume that every path containing
"/tags/" (case-insensitive) is a tag, and should be included in the tags
stack. Even better would be to allow the user to define what the tags
area is called. We already use a fixed "/tags/" check to issue a warning
about committing to a tag, so it's not an outrageous idea. Of course it
may differ between repositories, but there's no easy way around that.
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest Interface to (Sub)Version Control
/_/ \_\ http://tortoisesvn.tigris.org
To unsubscribe, e-mail: email@example.com
For additional commands, e-mail: firstname.lastname@example.org
Received on Thu Feb 9 22:48:17 2006