зеркало из https://github.com/mozilla/gecko-dev.git
b9e9d2e942
There was only a single use of 'install-to-subdir' in all our manifests (which was removed in the previous commit). All the comments around it suggest that it was a giant hack. Removing it cleans up a lot of complexity and saves me the trouble of needing to support it in the new sourcedir based TestResolver. Differential Revision: https://phabricator.services.mozilla.com/D57170 --HG-- extra : moz-landing-system : lando |
||
|---|---|---|
| .. | ||
| devtools/migrate-l10n | ||
| docs | ||
| gdbpp/gdbpp | ||
| l10n | ||
| lldbutils | ||
| mach | ||
| mozboot | ||
| mozbuild | ||
| mozlint | ||
| mozrelease | ||
| mozterm | ||
| mozversioncontrol | ||
| safety | ||
| README | ||
| mach_commands.py | ||
| moz.build | ||
README
This directory contains common Python code. The basic rule is that if Python code is cross-module (that's "module" in the Mozilla meaning - as in "module ownership") and is MPL-compatible, it should go here. What should not go here: * Vendored python modules (use third_party/python instead) * Python that is not MPL-compatible (see other-licenses/) * Python that has good reason to remain close to its "owning" (Mozilla) module (e.g. it is only being consumed from there). Historical information can be found at https://bugzilla.mozilla.org/show_bug.cgi?id=775243 https://bugzilla.mozilla.org/show_bug.cgi?id=1346025