Feature #5665

Subversion: there is no information about property changes

Added by Anonymous over 7 years ago. Updated over 5 years ago.

Status:NewStart date:2010-06-10
Priority:NormalDue date:
Assignee:-% Done:


Target version:-


If you view any revision changes via projects/x/repository/revisions/5772 or projects/x/repository/revisions/5772/diff you can't see any property changes. Property changes are very important especially when merging changes between different branches.

I'm using Redmine 0.9.4 with subversion.

Related issues

Duplicated by Redmine - Feature #6877: Add prop (property) changes to revision diffs Closed 2010-11-12
Duplicated by Redmine - Defect #6876: Diff view truncating lines shouldn't be counting SVN props Closed 2010-11-12


#1 Updated by Felix Schäfer over 7 years ago

Do you have a resource explaining what property changes are and maybe even what they are good for?

#2 Updated by Anonymous over 7 years ago

Properties in general:

But the most important is svn:mergeinfo property:
With this you see that a commit was actually a merged revision. Btw. if you view branch (any directory in fact) in repository browser it should show mergeinfo property so you could know which revisions are merged to that branch.

For example this is very well made in Trac http://trac.edgewall.org/ repository browser. Simply example here:

U can see there right now "svn:mergeinfo set to" and bottom are listed branches with merged and eligible info. If you move mouse over them you can see which revisions are merged and which are missing.

#3 Updated by Halle Winkler about 7 years ago

I have a similar usability issue with Subversion property changes. The property change that I have to use sometimes is to change the commit message after a version has been committed, because I have apps going up on the iTunes app store and I don't know whether the version is the version that was accepted for sale until 5 days after it was committed, which means that I need to change the commit message from something along the lines of "submitted 1.1 version" to "accepted 1.1 version" in order to make good use of having a versioning system. When I make a property change to a revision with an existing commit message in the following way:

svnadmin setlog local/path/to/repository -r 999 file.txt --bypass-hooks

The commit message is updated in svn, which can be verified by running:

svn -r 999 log

inside of the working copy, but the commit message is never updated in the repository tab of Redmine, even if I reboot and even if I attempt to run fetch_changesets (which always fails with an error). I hope there is a workaround for this since seeing the new commit message is actually pretty important for avoiding regressions. Thanks!

#4 Updated by Raphael Kallensee almost 7 years ago

I agree, svn properties are very important - and should get shown in revisions as well as the regular repository browser. We use svn-externals a lot (which are also set as svn-properties), there's currently no way to view them in Redmine.

@Halle Winkler: As far as I know, commits and their messages are cached by Redmine (tables "changes" and "changesets" e.g.). The only way might be to delete some lines in the respective database tables - but I don't think that's a good idea...

#5 Updated by Jean-Philippe Lang almost 7 years ago

  • Category set to SCM

#6 Updated by Toshi MARUYAMA over 6 years ago

  • Tracker changed from Defect to Feature

#7 Updated by Ве Fio over 6 years ago

+1 +1 +1
Would be really useful to see the property changes as well.

#8 Updated by Gilles Cornu about 6 years ago

+1. It is a standard (and very comfortable) feature on Trac.

#9 Updated by Terence Mill about 6 years ago


#10 Updated by Steve Davis about 6 years ago


#11 Updated by Thomas Oppelt over 5 years ago

+1 (this missing feature still prevents us from dropping trac's svn web view)

Also available in: Atom PDF