Project

General

Profile

Actions

Feature #5665

open

Subversion: there is no information about property changes

Added by Anonymous over 13 years ago. Updated over 4 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
SCM
Target version:
-
Start date:
2010-06-10
Due date:
% Done:

0%

Estimated time:
Resolution:

Description

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

Has duplicate Redmine - Feature #6877: Add prop (property) changes to revision diffsClosed2010-11-12

Actions
Has duplicate Redmine - Defect #6876: Diff view truncating lines shouldn't be counting SVN propsClosed2010-11-12

Actions
Actions #1

Updated by Felix Schäfer over 13 years ago

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

Actions #2

Updated by Anonymous over 13 years ago

Properties in general:
http://svnbook.red-bean.com/en/1.5/svn.advanced.props.html

But the most important is svn:mergeinfo property:
http://svnbook.red-bean.com/en/1.5/svn.branchmerge.basicmerging.html#svn.branchmerge.basicmerging.mergeinfo
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:
http://trac.edgewall.org/browser/branches/0.11-stable

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.

Actions #3

Updated by Halle Winkler over 13 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!

Actions #4

Updated by Raphael Kallensee over 13 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 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...

Actions #5

Updated by Jean-Philippe Lang over 13 years ago

  • Category set to SCM
Actions #6

Updated by Toshi MARUYAMA almost 13 years ago

  • Tracker changed from Defect to Feature
Actions #7

Updated by Ве Fio almost 13 years ago

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

Actions #8

Updated by Gilles Cornu over 12 years ago

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

Actions #9

Updated by Terence Mill over 12 years ago

+1

Actions #10

Updated by Steve Davis over 12 years ago

+1

Actions #11

Updated by Thomas Oppelt almost 12 years ago

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

Actions #12

Updated by Omar Zohary over 4 years ago

Is there any update on when this might be implemented.
I'm using

Environment:
  Redmine version                4.0.2.stable
  Ruby version                   2.5.5-p157 (2019-03-15) [x86_64-linux]
  Rails version                  5.2.2
  Environment                    production
  Database adapter               Mysql2
  Mailer queue                   ActiveJob::QueueAdapters::AsyncAdapter
  Mailer delivery                smtp
SCM:
  Subversion                     1.12.0
  Cvs                            1.12.13
  Git                            2.19.1
  Filesystem                     
Actions

Also available in: Atom PDF