I think the major issue that Subversion does tagging and branching "by
copy". So, copy has a link to the source, but there is no link from the
source to all copies. What I suggested is to work around that by
creating custom property where svn client app would put link to the
target when doing copy.
Another possibility could be to add a second "implicit" commit after
copy (tag or branch) operation that would change/touch property in both
source and target resources, so it would appear in "affected paths"
where it could be extracted from.
Both cases may not be very effition when done on the client, but I
wanted to throw the idea on the air, so people with more knowledge about
svn internals can comment on this.
regards,
Eugene
Zsolt wrote:
> What about with aliases? For example I could assign to the revision
> "10" the label "release-1.5-RC1" and to the revision "13" the label
> "release-1.5-final" and where the revision numbers are shown in
> brackets (or somehow) the assigned alias label could be also
> displayed. Would it be difficult to implement something like that?
>
>
>
> This would be a huge help. Because a revision number is valid for the
> entire repository this should work (not like in CVS where each file is
> versioned independently). The lack of this feature doesn't let us to
> move to subversion from CVS.
>
>
>
> Zsolt
>
>
>
> ------------------------------------------------------------------------
>
> *From:* Eugene Kuleshov [mailto:eu@md.pp.ru]
> *Sent:* Friday, December 02, 2005 6:40 PM
> *To:* users@subclipse.tigris.org
> *Subject:* Re: 0.9.100 How to compare to a tag or branch?
>
>
>
> Mark,
>
> How about add a special property where Subclipse would add target
> url when particular resource is copied? Then history view can read
> this property and offer a comparison.
>
> Later the same propery could be supported by other tools.
>
> regards,
> Eugene
>
>
> Mark Phippard wrote:
>
>Marc Sherman <msherman@projectile.ca> <mailto:msherman@projectile.ca> wrote on 12/02/2005 09:10:53 AM:
>
>
>
>
>
>>That would let you quickly populate a branch/tag browser with all the
>>
>>tree root paths. It's not optimal, because you'd need to update the
>>
>>property's value whenever you added a new branch/tag structure to your
>>
>>repo, but that happens fairly infrequently, so it's not awful, I don't
>>
>>think.
>>
>>
>>
>>Actually, this kind of thing could be implemented entirely in the client
>>
>>-- you could implement support for something like this in Subclipse
>>
>>without waiting for the svn command line client, and then add support
>>
>>for whatever tags the svn developers settle on if/when they do.
>>
>>
>>
>
>
>We should probably wait until the devs decide on a course of action. If
>
>they decide not to do anything, then we could invent our own system.
>
>
>
>I think your idea will be a lot harder to implement in a GUI then you
>
>think. I recall your idea relied on simplifying what a user typed. They
>
>typed something minimal, and then RegEx or something like that was used to
>
>transform that into a URL. To provide a GUI, you would need to be able to
>
>either query the repository using a RegEx, or you would have to recursive
>
>list of the repository and filter it yourself using an expression. The
>
>first option does not exist, and the second is going to be glacial in
>
>performance.
>
>
>
>Regardless, I hope this is something you are willing to contribute to the
>
>project as several people would like it.
>
>
>
>Mark
>
>
>
>
>
Received on Sat Dec 3 05:11:31 2005