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

Re: Antwort: Re: use case: which tags are implementing a specific feature which was realized in revision X? [*]

From: John Peacock <john.peacock_at_havurah-software.org>
Date: 2007-10-11 15:01:36 CEST

Lutz.Dornbusch@fiducia.de wrote:
> Again: In CVS it was a trivial task, and I need it for _all_ tags.
> At the moment I think I have to write a script which loops through all
> files and looks into each tag.

CVS is a file-oriented VCS, whereas Subversion is a repository-oriented
VCS. Consequently, some of the information that CVS provided
automatically is not explicitly stored in Subversion. The data you are
looking for is, unfortunately, one of those things which Subversion
doesn't support. This is unfortunately something you should have
discovered before you converted, rather than after.

At this point, you are indeed going to have to write a script to
ascertain this information; I am not aware of any general purpose tool
for performing this kind of introspection. Indeed, it may not be
possible to create a truly general tool for this, since your development
style may be very different from others in a similar situation.

I wish I could be more helpful. There is some hope for the future
though, since there has been some talk about adding a copy-to property
(though possibly not until 2.0). This would likely be a multivalued
property that would record (e.g. in trunk) where a given revision was
copied to (e.g. a tag). This information would allow you to generate a
file's history from trunk and get the tags for free, which would be
precisely the data you are looking for.

HTH

John

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Oct 11 15:02:09 2007

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.