That's the use case! :)
As I mentioned in a previous email, we're looking to
see if the equivalent functionality from cvs is
possible in svn. In that, we want to see what
revisions of a file was included in various tags.
As Karl alludes, it's not always just finding the
different copies of the trunk, as tags are taken off
of branches as well.
But it is for the purpose of seeing if released code
(denoted via a tag) contains a specific revision of a
file, to determine if released code has or has not
known problems.
Karl said it better.
It sounds like it doesn't have it, and we can live
with that. I was just attempting to make sure that
there wasn't a way of getting at this information
easily, and I just wasn't aware.
--- kfogel@collab.net wrote:
> Ryan Schmidt <subversion-2005@ryandesign.com>
> writes:
> > What is the use-case? What is the problem you are
> trying to solve,
> > the question you are trying to answer?
>
> How about the use case "In which releases did we
> ship exactly rNNN of
> file foo.c?", a question you might need to ask if
> you've recently
> learned that foo.c contains a dangerous bug.
>
> I've wanted this feature in Subversion for a long
> time, too. Of
> course, it can be implemented as an external DB
> outside the Subversion
> repository, but it would be nice if Subversion had a
> way to say "Show
> me all paths by which a given 'node revision' may be
> reached". That
> is equivalent to showing all the tags and branches
> it's on.
>
> -Karl
>
> --
> www.collab.net <> CollabNet | Distributed
> Development On Demand
>
____________________________________________________
Do you Yahoo!?
Yahoo! Photos: Now with unlimited storage
http://au.photos.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Wed Sep 28 00:14:54 2005