author Gerald Squelart <>
Thu, 26 May 2016 19:24:35 +1000
changeset 371291 89a24835ba7432bffb9c0c095a98a619a5750658
parent 289120 ae64d16898395607093db2e2dd667b6544cb1f55
child 306729 29617b97dd36cecdfcb11340f8ea2e7c3c729b68
child 313991 53c9d4821a559e9ecdd38726af0f6c6d8107082e
child 326860 99b39cd9daa267fae6cd95a0192b1cd1e093d29a
child 348761 c5e638d867ae17cf212438c52db8dd73fc0be1e6
child 389835 5243745d0b77604f6105e07ab2edb0593def9257
child 394059 d04b5a591b84ef80cddd4446e80ff14814dbd51e
child 428217 293fca44fda4e7cc0970f71b12024a14a40267b4
child 433150 d6ca56a87cf1456bb2a786546788b03a78a70d94
child 454032 564b17f6d9323f3e2dfb7a550735681af2021ede
child 491484 2e0e6bcef472c68a6feec06c57096ea9af608313
child 496966 ba37a2701a763962b01f7f7fe178fca16ab6cecd
child 501891 146751ba88f6dde8972b83ed262bae517fa2459e
permissions -rw-r--r--
Bug 1271483 - p16. gtest for list-string functions - r?cpearce Because it is templated code inside a cpp, the test includes a copy of that code. When we make this more public, the test should then include the proper header instead. MozReview-Commit-ID: 3vOvaj5VVhm

An explanation of the Mozilla Source Code Directory Structure and links to
project pages with documentation can be found at:

For information on how to build Mozilla from the source code, see:

To have your bug fix / feature added to Mozilla, you should create a patch and
submit it to Bugzilla ( Instructions are at:

If you have a question about developing Mozilla, and can't find the solution
on, you can try asking your question in a
mozilla.* Usenet group, or on IRC at [The Mozilla news groups
are accessible on Google Groups, or 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:
            - or -