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

Re: Equivalent of cvs log?

From: Garrett Rooney <rooneg_at_electricjellyfish.net>
Date: 2005-02-11 21:46:03 CET

Norman Walsh wrote:
> I've recently switched one of my projects from CVS to Subversion.
> So far, everything is great. I have a question though. I used
> to have a process that used the output of 'cvs log' (which dumps
> the log of the whole repository) to build another artifact.
> Of course 'svn log' only shows me the log for the root directory. I
> can imagine building a tool that recursively searches the repository
> and issues svn log requests for all the files, but that seems like
> overkill. Is there an easier way?

Just run 'svn log' on the root of the repository (or just the project in
question, if you have more than one project in the repository), it'll
show you the log entries for everything under it.

Another problem you might be having is when you make a change to a file,
the revision number of the directory it's in is not bumped up (for a
number of reasons related to mixed revision working copies), so if
you're doing 'svn commit -m "foo" file.c && svn log' you're not going to
see the latest change to file.c in the log output because log's target
defaults to the current directory at whatever revision your working copy
is at. You have to insert a 'svn update' in the middle, to force the
directory's version number to catch up to the commit you just made.


To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Fri Feb 11 21:49:46 2005

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.