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

RE: Communicating through the VC tool

From: <andy.glew_at_amd.com>
Date: 2004-04-02 21:38:42 CEST

> In Subversion, you would
> (1) checkout a project's 'trunk': 'svn co trunkURL'
> (2) run 'svn ls -v branchURL' where branchURL is the 'branches'
> subdirectory of the same project.
> Voila, you can see which task branches exist and are still
> being worked
> on. The ones that are finished have presumably been deleted already.
> If you want to see specific commits to a project's task-branches, then
> run 'svn log -v branchURL'.

Unfortunately, my group has arranged our SVN repository as

   * svnrepo
      * trunk
         * module1
         * module2
      * branches
         * module1
            * imported-version-of-module2
         * module2
         * users
            * user1
               * module1
               * module2

I.e. to find all information about any versions of module1,
I have to wade through much info about many other modules.

I don't think there's any way of arranging such a hierarchical
tree so that all reasonable queries of a single module can be
answered (at least not if you allow inter-module dependencies).

The tool we have already talked about, a transitive closure
tree walker that tracks down all versions of a file/module,
is needed.

(This is the well known problem with relational databases:
they have trouble doing Bill-Of-Materials queries.)

Hmmm.... I can see how to do such a transitive closure tree
walker for all things still in the SVN tree. If they
have been deleted...?

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Apr 2 21:39:25 2004

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

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