mirror of
https://github.com/mozilla/gecko-dev.git
synced 2024-10-30 05:35:31 +00:00
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
07941e6963
======== https://hg.mozilla.org/integration/gaia-central/rev/cdbaff53710b Author: Andrew Sutherland <asutherland@asutherland.org> Desc: Merge pull request #26566 from asutherland/upgrade-emailjs Bug 1097421 - [email] Upgrade email.js omnibus bug. r=jrburke ======== https://hg.mozilla.org/integration/gaia-central/rev/c420852c9ac3 Author: Andrew Sutherland <asutherland@asutherland.org> Desc: Bug 1097421 - [email] Upgrade email.js omnibus bug. r=jrburke Land https://github.com/mozilla-b2g/gaia-email-libs-and-more/pull/353 See its individual commit comments and the bugs dependent on bug 1097421 for more info. Note that this also includes 2 autoconfig changes: - 126.com: This makes us consistent with 163.com, another mail domain also operated by netease which also uses the coremail mail server and whose ActiveSync implementation does not work so well with our implementation. This avoids its autodiscover exposure capturing us and causing us to use its ActiveSync implementation. This is basically required since the Mozilla ISPDB is not capable of overriding the ISP's entries. (Which is desired in most cases for many reasons, but being able to say "don't use that ActiveSync implementation!" would be helpful.) - yahoo.co.jp: Right now the ISPDB says to use POP3. Only with these fixes do we work with yahoo.co.jp's IMAP implementation, so (selfishly), it's better to do this for now than to change the ISPDB. |
||
|---|---|---|
| accessible | ||
| addon-sdk | ||
| b2g | ||
| browser | ||
| build | ||
| caps | ||
| chrome | ||
| config | ||
| content | ||
| db/sqlite3 | ||
| docshell | ||
| dom | ||
| editor | ||
| embedding | ||
| extensions | ||
| gfx | ||
| hal | ||
| image | ||
| intl | ||
| ipc | ||
| js | ||
| layout | ||
| media | ||
| memory | ||
| mfbt | ||
| mobile | ||
| modules | ||
| mozglue | ||
| netwerk | ||
| nsprpub | ||
| other-licenses | ||
| parser | ||
| probes | ||
| profile | ||
| python | ||
| rdf | ||
| security | ||
| services | ||
| startupcache | ||
| storage | ||
| testing | ||
| toolkit | ||
| tools | ||
| uriloader | ||
| view | ||
| webapprt | ||
| widget | ||
| xpcom | ||
| xpfe | ||
| xulrunner | ||
| .clang-format | ||
| .clang-format-ignore | ||
| .gdbinit | ||
| .gitignore | ||
| .hgignore | ||
| .hgtags | ||
| .lldbinit | ||
| aclocal.m4 | ||
| Android.mk | ||
| AUTHORS | ||
| client.mk | ||
| client.py | ||
| CLOBBER | ||
| configure.in | ||
| LEGAL | ||
| LICENSE | ||
| mach | ||
| Makefile.in | ||
| moz.build | ||
| mozilla-config.h.in | ||
| README.txt | ||
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:
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 (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.]
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:
ftp://ftp.mozilla.org/pub/firefox/nightly/latest-trunk/
- or -
http://nightly.mozilla.org/