gecko-dev/python
Andrew Halberstadt 13b127e919 Bug 1401309 - [mozversioncontrol] Merge get_modified_files and get_added_files into a single function, r=gps
There's currently a function for getting added files (A) and modified files
(M). We'll also eventually need the ability to get deleted files (D) and any
combination of the above, e.g (AM). Rather than creating a new function for
each possible case, let's have a single function where you can pass in which
modifiers you are interested in. With this patch, if you want all modified and
added files, you can do:

get_changed_files('AM')

By default 'ADM' is used.

This also adds a 'mode' option for git. This allows consumers to return staged
files, unstaged files or both. The default ('unstaged') keeps the current
behaviour in tact.

MozReview-Commit-ID: 9IA1bxaJS80

--HG--
extra : rebase_source : 160f650220ca9a35b4b116bc9fa13f28d84419fa
2017-09-20 10:06:11 -04:00
..
devtools/migrate-l10n Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00
mach Bug 1399989 - Add python/mach to flake8 linter. r=gps 2017-09-17 22:41:17 -04:00
mozboot Bug 1401166 - Skip Stylo dependency with ./mach bootstrap on OpenBSD. r=rillian f=gaston 2017-09-19 12:19:40 +00:00
mozbuild Bug 1401309 - [mozversioncontrol] Merge get_modified_files and get_added_files into a single function, r=gps 2017-09-20 10:06:11 -04:00
mozlint Bug 1392787 - [mozlint] Fix bugs in path filtering and add a test, r=jmaher 2017-08-23 06:33:06 -04:00
mozversioncontrol/mozversioncontrol Bug 1401309 - [mozversioncontrol] Merge get_modified_files and get_added_files into a single function, r=gps 2017-09-20 10:06:11 -04:00
mach_commands.py Bug 1339178 - Use pytest to run python-tests, r=davehunt 2017-08-29 14:50:33 -04:00
moz.build Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00
README Bug 1346025 - Move vendored python modules from /python to /third_party/python, r=ted 2017-05-25 11:48:03 -04:00

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