1483352 - remove a couple of dead prefs

Status: RESOLVED DUPLICATE of bug 1429421

(Firefox :: Settings UI, enhancement, P5)

Description

[Dakota]

User Agent: Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:60.0) Gecko/20100101 Firefox/60.0
Build ID: 20100101

Steps to reproduce:

these 3 are dead since FF62 (https://bugzilla.mozilla.org/1462398):
- devtools.gcli.jquerySrc
- devtools.gcli.lodashSrc
- devtools.gcli.underscoreSrc

fe. https://dxr.mozilla.org/mozilla-central/search?q=underscoreSrc

and 'dom.ipc.shims.enabledWarnings' is dead since FF60 (https://hg.mozilla.org/mozilla-central/rev/beaba4c0ac0c). see https://dxr.mozilla.org/mozilla-central/search?q=enabledWarnings

Comment 1

[David Olah]

AIUI, from the about:config or any other Firefox interface, it is not possible today to clean up preferences, but having more or less preferences does not impact performance or functionality.

From what I know there are no known procedures in how to handle "dead" preferences. I also don't know if the listed preferences are really dead, so I will mark the issue as an enhancement and set component Preferences.

Comment 2

[Sören Hentzschel]

Attachment: Bug 1483352 - remove dead gcli preferences from devtools-shared.js

Comment 3

[Mike Conley (:mconley) (:⚙️)]

Comment on attachment 9005854 [details]
Bug 1483352 - remove dead gcli preferences from devtools-shared.js

Mike Conley (:mconley) (:⚙️) has approved the revision.

Comment 4

[Narcis Beleuzu [:NarcisB]]

Sören, there were conflicts applying your patch. Please fix and attach the new version.

Error: We're sorry, Autoland could not rebase your commits for you automatically. Please manually rebase your commits and try again. (255, 'applying /tmp/tmpHWZvr7\npatching file devtools/shared/preferences/devtools-shared.js\nHunk #1 FAILED at 70\n1 out of 1 hunks FAILED -- saving rejects to file devtools/shared/preferences/devtools-shared.js.rej\nabort: patch failed to apply', '')

Comment 5

[Sören Hentzschel]

Oops. I wanted to rebase the patch and did a `hg pull`. Then I saw there is a `hg pull --rebase`and found in the documentation:

> If you had done a normal hg pull without --rebase after your hg commit, you will have to first undo that by doing hg rollback.

But I can't execute `hg rollback` because of:

> abort: rollback is disabled because it is unsafe

What is the best way forward?

Comment 6

[Mike Conley (:mconley) (:⚙️)]

Hi Soren,

This is what I'd do:

1) Find the SHA of the commit you want to rebase. I assume this is still where your current working directory is at, so I'd do | hg log | or | hg summary | to get that.

Let's pretend that SHA is abcd1234

2) Once you have that, I think you can tell Mercurial to rebase that onto "tip" (which should be the most recent commit from central that you'd pulled down).

| hg rebase -r abcd1234 --dest tip |

And that should do it. Then you can | hg update | to tip, and push to Phabricator from there.


Does that work?

Comment 7

[Sören Hentzschel]

Yes, that worked! But I noticed the preferences from comment #0 have been removed by the patch in bug 1429421, so there is nothing more to do here. I will mark this bug as duplicate of bug 1429421. At least now I know how to rebase in Mercurial. I am sure I will need this sometime in the future. Thank you, Mike! :)