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

RE: how can we get list of all tags for a file

From: Aditya Gandhi <agandhi_at_sapient.com>
Date: 2004-06-07 16:10:04 CEST

That would assume that all the files that need tagging get tagged in a
single operation..
However, that is not the case with us.

In the past we have selectively tagged files as and when they get

Also, we right now tag files selectively in a folder i.e. I may end up
tagging only 3 of 5 files in a folder.. therefore when the actual
tagging happens it can not be a single and simple operation like copy a
base folder.. we end up going file by file across folders and tagging

I know this is not the best tagging strategy and I hope that we will
change that in the near future. However, till that time we will need a

Do let me know your thoughts on this.
Thanks for your response John.

- Aditya Gandhi

  -----Original Message-----
  From: John Peacock [mailto:jpeacock@rowman.com]
  Sent: Monday, June 07, 2004 7:31 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 think the most important use of this will be to figure out what
> changed between two baselines i.e. changes between two tags
> Say for example I baseline my requirements/ design and code at a
> 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
> in my application. (note: dates do not work for me so I need to rely
> tags)
  You can obviously get at the actual file changes by doing a diff
  the two tags (or in your case tag and trunk). More than that, you can
  use 'svn log -r' to get at the changes committed to the trunk since
  whatever revision you made the tag (which you have to get at via 'svn
  log' on the tag). If you use both '-q -v' options to 'svn log' you
  get the changed path information for each revision, but not the
  individual log messages themselves. It shouldn't be too hard to write
  quick script to grab the output from 'svn log -q -v -r ####' and
  a nice sorted report related what files were changed when.
  It's not that the imformation doesn't exist, it's just that is not
  stored seperatedly in the repository (like in CVS) and needs to be
  extracted when needed.
  John Peacock
  Director of Information Research and Technology
  Rowman & Littlefield Publishing Group
  4501 Forbes Boulevard
  Suite H
  Lanham, MD 20706
  301-459-3366 x.5010
  fax 301-429-5748

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Mon Jun 7 16:12:40 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.