Trivial change to force new round of builds, trying to resolve bug 581888 by backing out mac64 mozconfig changes
authorNick Thomas <nthomas@mozilla.com>
Mon, 26 Jul 2010 20:51:40 +1200
changeset 48199 5cda23bbfc29e49822a8d01b2c7876fd064bc32a
parent 48198 3559a37d183fd192c29e67e3120f9983bc843340
child 48200 2f2dd2813d17d0e259a276563d4d7aef7bc57067
push idunknown
push userunknown
push dateunknown
bugs581888
milestone2.0b3pre
first release with
nightly linux32
5cda23bbfc29 / 4.0b3pre / 20100726030126 / files
nightly linux64
5cda23bbfc29 / 4.0b3pre / 20100726030713 / files
nightly mac
5cda23bbfc29 / 4.0b3pre / 20100726030711 / files
nightly win32
5cda23bbfc29 / 4.0b3pre / 20100726040625 / files
nightly win64
5cda23bbfc29 / 4.0b3pre / 20100726024854 / files
last release without
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
releases
nightly linux32
nightly linux64
nightly mac
nightly win32
nightly win64
Trivial change to force new round of builds, trying to resolve bug 581888 by backing out mac64 mozconfig changes
README.txt
--- a/README.txt
+++ b/README.txt
@@ -3,17 +3,17 @@ project pages with documentation can be 
 
     https://developer.mozilla.org/en/Mozilla_Source_Code_Directory_Structure
 
 For information on how to build Mozilla from the source code, see:
 
     http://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 (http://bugzilla.mozilla.org). Instructions are at:
+submit it to Bugzilla (https://bugzilla.mozilla.org). Instructions are at:
 
     http://developer.mozilla.org/en/docs/Creating_a_patch
     http://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 http://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.]