|Group||Application User Guides|
Dealing with huge changesets, and when not to use Differential.
When you want code review for a given changeset, Differential is not always the right tool to use. The rule of thumb is that you should only send changes to Differential if you expect humans to review the actual differences in the source code from the web interface. This should cover the vast majority of changes but, for example, you usually should not submit changes like these through Differential:
You can still try submitting these kinds of changes, but you may encounter problems getting them to work (database or connection timeouts, for example). Differential is pretty fast and scalable, but at some point either it or the browser will break down: you simply can't show nine million files on a webpage.
More importantly, in all these cases, the text of the changes won't be reviewed by a human. The metadata associated with the change is what needs review (e.g., what are you checking in, where are you putting it, and why? Does the change make sense? In the case of automated transformations, what script did you use?). To get review for these types of changes, one of these strategies will usually work better than trying to get the entire change into Differential:
These kinds of changes are generally rare and don't have much in common, which is why there's no explicit support for them in Differential. If you frequently run into cases which Differential doesn't handle, let us know what they are.