diff options
| author | Chris Tate <ctate@google.com> | 2010-10-29 12:57:04 -0700 |
|---|---|---|
| committer | Chris Tate <ctate@google.com> | 2011-01-09 13:01:45 -0800 |
| commit | bbff7ed44b353ff299b900a1ff50812a082206f0 (patch) | |
| tree | 6b95c316e1f113c1c7af257217708d9282218a4b /graphics/java/android/renderscript/ProgramFragmentFixedFunction.java | |
| parent | 6ec91731cbf6ee1a9a914d341fab9567d1599018 (diff) | |
DO NOT MERGE : Ensure that the first post-restore backup pass is correct
Some restore passes bring an ancestral dataset to the application, but
others instead act to bring an app back into sync with its own most-
recently-saved data. In the latter case the state file written by the
app after the restore is a correct basis for generating future backup
deltas, but in the former case it is not.
The app should not be required to distinguish between these cases;
the framework has all the information necessary to handle the saved
state correctly following any flavor of restore operation. This
patch makes the Backup Manager properly cause a full backup pass
following an ancestral-dataset restore. After a current-set
restore the saved state file is an accurate description for
purposes of continued backup operations, so is preserved.
(Cherrypick from master to gingerbread)
Change-Id: I4bc4e8782a168ecc0795107a340bdbb35060730e
Diffstat (limited to 'graphics/java/android/renderscript/ProgramFragmentFixedFunction.java')
0 files changed, 0 insertions, 0 deletions