Makoto Onuki c14ff6ea45 Fix handling IOException in ImapStore ... - mConnection.destroyResponses() should be protected with if (mConnection != null). When we get an IOException, we close the connection and null it out in ioExceptionHandler(). So mConnection can be null at any point after where ioExceptionHandler() first appears. - ioExceptionHandler should close its parent ImapFolder only if the argument connection is mConnection. Methods like exists() may pass an ImapConnection which is not mConnection to ioExceptionHandler. In which case we don't have to close the ImapFolder. Bug 2898211 Change-Id: I8f9f45d91f596bb8da1a1575593e652d66deb643		2010-08-11 14:44:09 -07:00
assets
docs
images
res	Merge "translatable="false" for untranslatable strings."	2010-08-09 11:01:32 -07:00
src	Fix handling IOException in ImapStore	2010-08-11 14:44:09 -07:00
tests	Fix handling IOException in ImapStore	2010-08-11 14:44:09 -07:00
.classpath
.project
Android.mk	add filter for emma code coverage	2010-06-17 11:25:07 -07:00
AndroidManifest.xml	Make Welcome launch MessageListXL	2010-08-05 13:58:20 -07:00
CleanSpec.mk	Add an empty CleanSpec.mk	2010-03-08 18:05:00 -08:00
MODULE_LICENSE_APACHE2
NOTICE
proguard.flags	Fragmentize AccountSettings	2010-08-09 10:36:50 -07:00
remove-exchange-support.sh