Download Latest Version QuickRev-2025.17.bin.zip (9.3 MB)
Email in envelope

Get an email when there's a new version of QuickRev

Home / OldFiles / 3.3.2
Name Modified Size InfoDownloads / Week
Parent folder
QuickRev-3.3.2.src.zip 2020-03-28 8.2 MB
README-3.3.2.txt 2020-03-28 1.9 kB
QuickRev-3.3.2.bin.zip 2020-03-28 7.5 MB
Totals: 3 Items   15.7 MB 0
+--------------------------------------------+
| Take a look at                             |
| http://quickrev.sourceforge.net/news/      |
| for a complete overview (with screenshots) |
+--------------------------------------------+

-  QuickRevBoard: New option '--replace-path-ext' for an extended replacement of the paths to the project files or even the files to be reviewed. In difference to the '--replace-path' option the 'replace-to' string will not be escaped, so it becomes possible to make use of capturing groups. Take a look at the help for examples.

-  When merging project files in GIT to a different branch the commit hashes referenced in the review sheet might not be available on the new branch, in this case QuickRev tries to find the files by their file hash (SHA1) in the history of the file and uses the found commit hash instead. If the file content cannot be loaded via the commit hash the SHA1 of the file will be used instead.

-  Updated version of H2-DB to H2 1.4.199.

-  fix: When loading a changeset in GIT for a concrete commit hash the changeset was not loaded in case an invalid default GIT repository was assigned in the preferences.

-  fix: When starting QuickRev for GIT with '--git-log-m' or '--git-log-follow-m' and either a concrete changeset was loaded or a range of changesets the changesets which are merge commits have not been visible. It now works even when starting QuickRev with the options '-cs <commit-hash>'.

-  fix: When loading changesets the latest version of a file was loaded instead of the version defined by the changeset itself.

-  fix: NullPointerException during edition of path in 'Changeset Selection' dialog

-  fix: When loading files which are not under version control in diff-mode a "MalformedInputException: Input length = 1" occurred in case the file had no valid UTF-8 encoding.
Source: README-3.3.2.txt, updated 2020-03-28