ContributionsMost RecentMost LikesSolutionsRe: Using 'last' in ccollab commandsSeparate invocations of `ccollab` can certainly have other invocations of `ccollab` that use the same configuration file between them so there is a concurrency concern. To avoid that, use `ccollab admin batch`. The value for `last` is consistent within each invocation, and you can put as many commands in a single batch-xml spec as you want.Re: ERROR: You do not have access to perform this action:There is a bug in 5.0.5040 in the Perforce implementation. There is no fix released yet, please use an earlier version of the client software.Re: New Review Upload SubversionIf you mean you've got a feature branch with a few commits and you want to start a review, you could just add each commit, or you could upload the diffs between the branch point and HEAD within that subtree. That would look roughly like: ccollab addsvndiffs -r OLD:HEAD svn://domain/path/to/branch/ If you mean you want to review your entire codebase in one big shot, I'd strongly advise against it. If you must, diff the root of your project against an empty folder. (you may need to check one in) ccollab addsvndiffs svn://path/to/empty svn://path/to/project/rootRe: p4v integration on Linux doesn't workWe've found good reason to suspect this is a bug introduced in recent versions of P4V. This has been solved at lease once with `touch ~/.p4qt/customtools.xml`Re: Can you mark sections of code as "do not review"There is nothing explicit, but you can always leave a comment to that effect.Re: Keyword Find in diff viewer?Most browsers provide a search via Ctrl+F. CodeCollaborator doesn't have an additional featureRe: What is the purpose of the "Accept" action?Generally the accept button puts a green checkmark on the review overview screen. You are not required to "accept" anything for a review to complete. Accepts in the "Overall" conversation for a file can be used to indicate the 'latest accepted' version when you are using 'latest accepted' as your default previous version.