зеркало из https://github.com/mozilla/gecko-dev.git
5f3289da9a
Detecting the upstream repository isn't always possible. Using 'git merge-base' seems to be a more reliable way of detecting outgoing files. MozReview-Commit-ID: 3zOdTRIcggw --HG-- extra : rebase_source : 56dfd16bbddca38195f6a833dc5696cf509f3fa8 |
||
---|---|---|
.. | ||
devtools/migrate-l10n | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozversioncontrol | ||
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