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

Re: 0.9.100 How to compare to a tag or branch?

From: Marc Sherman <msherman_at_projectile.ca>
Date: 2005-12-02 15:10:53 CET

Mark Phippard wrote:
>
> I do not see this feature getting any easier to use for the forseeable
> future. I about all I can see improvements in is showing the output
> graphically instead of as a diff, but the process to invoke the compare is
> not likely to change. There have been talks in the Subversion lists on
> adding some new capabilities to make this easier but it is hard to tell if
> they have settled on anything or when they plan to implement it. Also,
> their ideas seems very geared towards power users and the command line. I
> am not sure how easily we will be able to leverage those features if they
> do implement them.
>
> Being able to easily see the tags associated with a specific revision in
> this history view is not likely to ever happen. The current design of
> Subversion makes it impossible and the area of the design that effects
> this is so core to Subversion and a lot of its features that I do not
> anticipate them changing their design for this feature.

Assuming something like my projectroot/treeroot proposal is adopted, all
you'd need is one more tag at the projectroot with a list of paths to
treeroots, which Subclipse could then use to generate the tag/branch list.

Consider the following tree:

/projectA
   /trunk *
   /branches
      /br1 *
      /br2 *
   /tags
      /tag1 *
      /tag2 *
   /releases
      /1.x
        /1.1 *
        /1.2 *
      /2.x
        /2.1 *
        /2.2 *

The /projectA dir would have the projectroot tag. Every dir marked with
a * would have the treeroot tag. For GUI branch/tag selection support,
you'd have to add one more tag, on projectA:

treerootpaths = 'trunk
branches/*
tags/*
releases/*/*'

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.

- Marc
Received on Sat Dec 3 01:10:53 2005

This is an archived mail posted to the Subclipse Users mailing list.

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