neluvasilica
Regular Visitor
Joined 7 years ago
User Profile
User Widgets
Contributions
document compare
I often find most of the changes are boilerplate changes, typically the date and/or document revision number in the footer. This means “jump to next change” is not particularly helpful since it takes me through each footer of every page. I know it will be non-trivial, but it would be amazing if there would be a way to skip this sort of boilerplate change that changes on every revision and isn’t really a change.775Views2likes1CommentSVN import failed as a result of file merging
Since Collaborator uses the Subversion command-line client and its native commands to fetch the data from the local SVN repository or the SVN server, Collaborator will abort the entire uploading process if at least one of the outputs of the native commands will be unexpected or contain an error. This is done to prevent losing data or uploading the incorrect files to the Collaborator server. It would be good if CodeCollaborator would be able to handle importing a review from which a file has been removed during a merge to handle this differently. i.e: continue to import the files it could parse, and maybe put up a warning or something, rather than aborting the import.