README.txt
author Mike Hommey <mh+mozilla@glandium.org>
Thu, 05 Oct 2017 13:05:54 +0900
changeset 385647 ab7615bac4ee05b8371a7f9571ca88fb482a073f
parent 348733 40911fc4bf7eff4f84add35cceb3a67d69a6e75a
child 417348 3c5ec0ff49dc7239a6e72d311e04b047ad6d50fc
permissions -rw-r--r--
Bug 1407464 - Remove probes/. r=ted The files generated from the contents of probes/ are never used even with dtrace enabled, and mozilla-trace.d actually never contained probes definitions. The js engine has probes of its own, and separate scripts to generate the corresponding source headers. (see e.g. js/src/devtools/javascript-trace.d)

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/