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

Traceability of svn log

From: Thomas Mauch <thomas.mauch_at_gmx.net>
Date: Mon, 27 Oct 2008 21:43:34 +0100

I was experimenting with svn log to trace the actions applied to the
Subversion repository. The basic idea was that it should be possible to
detect what happened to the files at a high level by just looking at the svn
log output. And on the first look it seems that svn log has been written
with this idea.

However there are a few subtleties which are not fully covered. So I am not
able to distinguish between the two different actions
1) copy file f1 to f2, commit
2) copy file f1 to f2, modify file f2, commit
As a consequence if I see an Add action in the svn log output, I have to
access the repository and make a diff between file1 and file2 to detect
whether it has just been copied or it has also been modified.

The same is true for renaming files. When searching around, I found the
rename cases mentioned in presentation "Subversion 1.4 true renames
problems" appended to issue 898. However I found no further information how
this shortcomings of svn log should be addressed by issue 898. Are there
further information available?

IMHO it should be the clear objective that the output of svn log provides
you with all the information you need to trace actions on files without
having to access the repository. And this should hold for property changes
as well, so you could easily distinguish the cases 1 and 2 from
3) copy file f1 to f2, change property of file f2, commit

What do you think?

To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org
Received on 2008-10-27 21:44:03 CET

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.