diff options
| author | mark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-20 22:01:35 +0000 |
|---|---|---|
| committer | mark@chromium.org <mark@chromium.org@0039d316-1c4b-4281-b951-d872f2087c98> | 2011-06-20 22:01:35 +0000 |
| commit | ab376cae3cd176f4aae8d67a5274891b66d9beda (patch) | |
| tree | e96c4236f1692bd2bd209e36d4347a11edc18a1e /chrome/browser/mac | |
| parent | e0b85abaf8d69768c74c5fb381259b82564ca433 (diff) | |
| download | chromium_src-ab376cae3cd176f4aae8d67a5274891b66d9beda.zip chromium_src-ab376cae3cd176f4aae8d67a5274891b66d9beda.tar.gz chromium_src-ab376cae3cd176f4aae8d67a5274891b66d9beda.tar.bz2 | |
Get rid of ClearByPathBackupExclusion.
We planned on keeping ClearByPathBackupExclusion around as temporary code to
clean up the mess we used to make in
/Library/Preferences/com.apple.TimeMachine.plist. Evidently, when we ask
CSBackupSetItemExcluded to include-by-path an item that was previously
excluded by path, it will remove the ExcludeByPath entry for the path from
that plist, but it will also add an IncludeByPath entry. There is no way
using this API to clean up the mess we made in the past, we can only trade
an "exclude" mess for an "include" mess. It's not worth attempting to modify
the file ourselves, avoiding the CSBackupSetItemExcluded API, and it's
probably not even possible because the plist will likely be rewritten by
a system process anyway.
BUG=86845, 85999
TEST=No changes made to the plist mentioned above.
Review URL: http://codereview.chromium.org/7206030
git-svn-id: svn://svn.chromium.org/chrome/trunk/src@89741 0039d316-1c4b-4281-b951-d872f2087c98
Diffstat (limited to 'chrome/browser/mac')
0 files changed, 0 insertions, 0 deletions