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

Re: svn diff --summarize vs. svn log

From: Hari Kodungallur <hkodungallur_at_gmail.com>
Date: Mon, 12 May 2008 12:47:42 -0700

On Mon, May 12, 2008 at 11:20 AM, Bob Kuo <bob_at_marcelmedia.com> wrote:

> Hello,
> I am in the process of writing a script that will one-way sync from a
> repository to an FTP server. The idea is that multiple users would make
> changes on the repository, and when we wanted those changes on the server,
> we would run the script. We would get a list of changes made since the
> last
> revision that was uploaded and then set the ftp client to upload each one
> of
> those changes.
> As far as I can tell, there are two ways to get a list of changes between
> two revisions: svn diff --summarize and svn log. The problem with svn
> log
> is that it doesn't summarize, that is, a file edited across multiple
> revisions will show up multiple times in the log. The problem with svn
> diff
> --summarize is that it doesn't track files that have been moved.
> Is there a good way to get this summary information that will track files
> that have been moved?

I am not aware of any other command as well. Probably best to script around
svn log.
If possible, you could try to get a post-commit hook that incrementally
creates this list of files after every commit. That is another option.
I suppose ftp is a requirement. If not, you could just do an rsync from an
updated working copy to update only the files that have changed.

Received on 2008-05-12 21:48:07 CEST

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.