mirror of
https://github.com/mozilla/gecko-dev.git
synced 2025-02-27 04:38:02 +00:00

Mercurial's sparse checkout support allows "profile" files defining what's in sparse checkouts to be defined in-tree. This convenient feature means you simply need to point a client at a path inside the repository and it dynamically resolves what files to include in the checkout. As you update revisions, the "profile" pulls in updates to the underlying file. We introduce 2 sparse profiles: 1 for mach and another for taskgraph. The goal of the "mach" profile is to provide enough files to run `mach`. If you activate this profile and run `mach`, it runs without error. But there are practically no commands available. So it isn't terribly useful. The "taskgraph" profile allows us to run `mach taskgraph`. This profile demonstrates a sparse profile feature: including other profiles. The "taskgraph" profile is thus a union of "mach" and its own entries. There is definitely some fat in these profiles. I didn't feel like chasing the long tail and getting overly granular with the profiles. If we want to optimize later, we can do that. For reference: Full checkout: ~234,000 files mach: ~2,000 files taskgraph: ~3,600 files MozReview-Commit-ID: 7pALt0MwHfE --HG-- extra : rebase_source : 1a4ba4b8a63c522dab2841e2c0019501476da2fe
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
…
An explanation of the Mozilla Source Code Directory Structure and links to project pages with documentation can be found at: https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure For information on how to build Mozilla from the source code, see: https://developer.mozilla.org/en/docs/Build_Documentation To have your bug fix / feature added to Mozilla, you should create a patch and submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at: https://developer.mozilla.org/en/docs/Creating_a_patch https://developer.mozilla.org/en/docs/Getting_your_patch_in_the_tree If you have a question about developing Mozilla, and can't find the solution on https://developer.mozilla.org, you can try asking your question in a mozilla.* Usenet group, or on IRC at irc.mozilla.org. [The Mozilla news groups are accessible on Google Groups, or news.mozilla.org with a NNTP reader.] You can download nightly development builds from the Mozilla FTP server. Keep in mind that nightly builds, which are used by Mozilla developers for testing, may be buggy. Firefox nightlies, for example, can be found at: https://archive.mozilla.org/pub/firefox/nightly/latest-mozilla-central/ - or - https://nightly.mozilla.org/
Description
Read-only Git mirror of the Mercurial gecko repositories at https://hg.mozilla.org. How to contribute: https://firefox-source-docs.mozilla.org/contributing/contribution_quickref.html
Languages
JavaScript
32.3%
C++
25.4%
HTML
21%
C
10.8%
Python
2.8%
Other
7.2%