Bugzilla

Note: don't be fooled by this error that's currently shown on https://phabricator.services.mozilla.com/D191985 (and only just appeared recently):
```
WARNING: The code review bot failed to apply your patch because the parent revision (64d8108d8774e55e8d6555f72dd37ecfb21713f2) does not exist on mozilla-unified. If possible, you should publish that revision.
```

That's the sort of error that I would have hoped to see there in the first place, to let me know that there were (originally) some merge conflicts.  But it wasn't there, and in fact it only just appeared after I rebased the patch onto a supporting patch locally (specifically https://phabricator.services.mozilla.com/D192116 , which is now `64d8108d8774e55e8d6555f72dd37ecfb21713f2` in my local tree.)

Anyway: the presence-of-that-error is not a huge deal; ideally it would go away after I hooked set up the parent-revision relationship to D192116, but it's fine. Mostly mentioning it since it superficially **looks** like it's the exact thing I'm requesting in comment 0 here, but in fact it's not (since it only appeared when I partially rebased and resubmitted the patch from moz-phab locally).

Note: don't be fooled by this error that's currently shown on https://phabricator.services.mozilla.com/D191985 (and only just appeared recently):
> WARNING: The code review bot failed to apply your patch because the parent revision (`64d8108d8774e55e8d6555f72dd37ecfb21713f2`) does not exist on mozilla-unified. If possible, you should publish that revision.

That's similar to the sort of error that I would have hoped to see there in the first place, to let me know that there were (originally) some merge conflicts.  But it wasn't there, and in fact it only just appeared after I rebased the patch onto a supporting patch locally (specifically https://phabricator.services.mozilla.com/D192116 , which is now `64d8108d8774e55e8d6555f72dd37ecfb21713f2` in my local tree.)

Anyway: the presence-of-that-error is not a huge deal; ideally it would go away after I hooked set up the parent-revision relationship to D192116, but it's fine. Mostly mentioning it since it superficially **looks** like it's the exact thing I'm requesting in comment 0 here, but in fact it's not (since it only appeared when I partially rebased and resubmitted the patch from moz-phab locally).