Project

General

Profile

Redmine resyncing a Subversion commit log that has been updated.

Added by Cheyenne Wills over 11 years ago

We've ran into a couple of situations where the commit log needed to be updated (wrong issue numbers, or incorrect info, etc). The Subversion log itself is updated (via propedit), however the Redmine "shadow" of the commit log isn't updated and there seems to be no way to cause Redmine to rescan a particular revision's log (yes, we are aware of deleting the repository from Redmine and re-adding the repository, but that is impractical due to the size of some of the repositories).

In one case, I manually updated the Redmine database with the corrected information (the commit log had some information that wasn't to be disclosed).

What I was wondering, does anyone have a tool, patch, or plugin that will tell Redmine to remove a single revision's commit log and rescan it from the SCM?


Replies (1)

RE: Redmine resyncing a Subversion commit log that has been updated. - Added by Cheyenne Wills over 11 years ago

(Oh.. I'm aware of an earlier message related to this (message 12161))

    (1-1/1)