Hi John,
Thanks for your reply.
I think the most important use of this will be to figure out what has
changed between two baselines i.e. changes between two tags
Say for example I baseline my requirements/ design and code at a point
of time and do a release. Before the next release I would like to be
able to create a report of what all has changed since the previous tag
in my application. (note: dates do not work for me so I need to rely on
tags)
This could be at a repository level or more granular at a file level. In
the past I have used the cvs log -rtag1::tag2 (along with some custom
parsing) to figure this out for my projects. This report used to include
list of files that have been added/ modified/ deleted along with details
of what versions were checked in with what comments).
However, I am struggling with how I can do that in SVN.
- Aditya Gandhi
-----Original Message-----
From: John Peacock [mailto:jpeacock@rowman.com]
Sent: Monday, June 07, 2004 4:15 PM
To: Aditya Gandhi
Cc: users@subversion.tigris.org
Subject: Re: how can we get list of all tags for a file
Aditya Gandhi wrote:
> I would like to know what command can be used to find a list of all
the
> tags that have been created for a file.
It's not [currently] possible in Subversion. CVS is file-centric, in
that
all
information about a particular file is stored in a single place in
repository.
Subversion is more repository-centric, in that a given revision is
merely
the
collection of all files at a point in time (whether you are talking
about
the
HEAD or any branch or tag revision).
I know that there are plans to support copy-to (where was this file
copied
to
during it's lifetime), which will be the other side of copy-from
(where
did this
file originally come from). However, this is strictly a 2.0 issue
(because of
the incompatible database changes), so you are talking about a while.
Perhaps if you told us /why/ you need to know this information, we can
suggest
other ways to handle it.
> Similarly seems like the equivalent of the cvs graph feature is
missing
> in subversion. Are there any thoughts on including that as a
standard
> feature or are some particular client tools implementing this?
That's a GUI feature; strictly speaking it is implemented by using
'cvs
log' and
parsing the output. And again, since Subversion does not currently
have
any way
of tracking when a file is copied to a tag or branch, it is not
possible
to
dummy up a complete analogue of this feature.
HTH
John
--
John Peacock
Director of Information Research and Technology
Rowman & Littlefield Publishing Group
4720 Boston Way
Lanham, MD 20706
301-459-3366 x.5010
fax 301-429-5747
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 7 15:01:11 2004