Since you asked here as well, I'll copy/paste my answer from https://phabricator.services.mozilla.com/D65217#2001705: You are probably working on top of your previous commit, so when you submit using moz-phab it keeps submitting the whole stack. try to: hg pull central (will fetch the latest changes from mozilla-central) hg update central (will move your repository to point to the latest mozilla-central changeset) Then you'll need to either redo your patch for Bug 1616244, or move your changeset for Bug 1616244 to the tip of central. You can use hg wip to visualize your repository, find your changeset. As an example, if you find that the hash of your changeset is abcdef123456, you can move it using hg rebase: hg rebase -s abcdef123456 -d central
Bug 1616244 Comment 9 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
Since you asked here as well, I'll copy/paste my answer from https://phabricator.services.mozilla.com/D65217#2001705: You are probably working on top of your previous commit, so when you submit using moz-phab it keeps submitting the whole stack. try to: - `hg pull central` (will fetch the latest changes from mozilla-central) - `hg update central` (will move your repository to point to the latest mozilla-central changeset) Then you'll need to either redo your patch for Bug 1616244, or move your changeset for Bug 1616244 to the tip of mozilla-central. You can use `hg wip` to visualize your repository, find your changeset. As an example, if you find that the hash of your changeset is `abcdef123456`, you can move it using `hg rebase`: `hg rebase -s abcdef123456 -d central`