)]}' { "commit": "d415303c4d02c1d30dd4199bade4694bf2cb4615", "tree": "8ed226002bb752d9df22fe51063083c79bf54a89", "parents": [ "3a5c054ac3a33753c3aeb2cb26e7b05d64291839" ], "author": { "name": "tao.pei", "email": "tao.pei@ck-telecom.com", "time": "Tue Jun 02 10:06:20 2015 +0800" }, "committer": { "name": "Narayan Kamath", "email": "narayan@google.com", "time": "Mon Jun 08 15:14:08 2015 +0000" }, "message": "Pass MUTF-8 paths to open(2) instead of UTF-8.\n\nModified UTF-8 and UTF-8 differ with respect to how they handle\nnon-BMP characters. Modified UTF-8 uses 2 x 3 byte encodings, one\neach for the high and low surrogate, whereas UTF-8 uses a single\n4 byte sequence.\n\nFile systems don\u0027t specify and encoding and therefore the file name\nencoding will vary depending on how it\u0027s created. All standard\nJava APIs (java.io.File / FileOutputStream etc.) use Modified UTF-8\nfilenames, so we assume that\u0027s the status quo.\n\nWe will also audit code from the rest of the platform to make sure\nthat file names are encoded consistently.\n\nbug: 21578056\n\nChange-Id: I8e37af7f7cc442805a48899917f8e61c8f81fba6\n", "tree_diff": [ { "type": "modify", "old_id": "4f29c50274231974ef7a93d67c78a5e706e91bbc", "old_mode": 33188, "old_path": "core/jni/android_os_Parcel.cpp", "new_id": "65eb38c452901e8c2978349dd6abf35c20551d99", "new_mode": 33188, "new_path": "core/jni/android_os_Parcel.cpp" } ] }