I should point out that these interdiff issues are being actively worked on.
At least one of them, bug 1238000[1], already has a patch that's under review to land in core[2]. Just be sure to file them. Having talked to the MozReview team about these types of bugs, I do know that trust-worthiness of diffs and interdiffs is very much a thing that we should be able to take for granted. Any bugs in diff and interdiff trust-worthiness are high-priority to fix. [1]: https://bugzilla.mozilla.org/show_bug.cgi?id=1238000 [2]: https://reviews.reviewboard.org/r/7874/ On 25 January 2016 at 11:28, Boris Zbarsky <bzbar...@mit.edu> wrote: > On 1/23/16 9:48 PM, Mike Hommey wrote: > >> Note that if /other/ changes from other bugs have happened to the same >> files between the last reviewed iteration and the rebase before landing, >> the interdiff will show them without any kind of visual cues. >> > > Ah, that's unfortunate. > > I agree that this is a hard problem, though (interdiff across rebases). I > guess that does mean that you can't really use the final attached thing for > the "I want to see the interdiff" use case; need to push something to > MozReview before rebasing to address that. > > > -Boris > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform > _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
