зеркало из https://github.com/mozilla/gecko-dev.git
529144ec47
A previous patch added parsing `git remote -v`, preferring `mozilla-unified` as the official upstream remote and falling back to the first official-looking remote if unified was not found. We assumed that a developer is either using mozilla-unified, or is using a single-headed repo like central. This overlooks the fact that it is possible to clone from central, and then pull other repos in, creating a repo with multiple official remotes. Update the `get_upstream_remote` function to find all official looking remotes instead of a single official remote, and change the `get_remote_arg` function to return a list of `--remotes` arguments to be passed to various Git commands. This allows Git to take all official remotes into consideration and more precisely find the commits which are not present on any official upsteams. Add a test for `get_mozilla_remote_args` while we are here. Differential Revision: https://phabricator.services.mozilla.com/D199637 |
||
---|---|---|
.. | ||
docs | ||
gdbpp/gdbpp | ||
l10n | ||
lldbutils | ||
mach | ||
mozboot | ||
mozbuild | ||
mozlint | ||
mozperftest | ||
mozrelease | ||
mozterm | ||
mozversioncontrol | ||
sites | ||
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