summaryrefslogtreecommitdiffstats
path: root/chrome/profile_import
Commit message (Collapse)AuthorAgeFilesLines
* Re-land r56742 now with correct database filesbrettw@chromium.org2010-08-212-3/+6
| | | | | | | | | | | | | | | | A new field to describe the sources of history urls(visits) is added. This field is recorded in visit_database. So far, it can tell imported, synchronized, entension added or other(mainly testing) entries from user browsed entries. In the future, history extension API may allow queries to combinate with this criterion. BUG=none TEST=Unit tests are already included. Please test the web browser with history from previous versions to make sure the migration could be done properly. Also try to import or sync some history and inspect the sources added to the visit_source table in hitory database are correct. Original review: http://codereview.chromium.org/2906004/show Patch by weili@google.com git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56971 0039d316-1c4b-4281-b951-d872f2087c98
* Revert 56742 - A new field to describe the sources of history urls(visits) ↵brettw@chromium.org2010-08-192-6/+3
| | | | | | | | | | | | | | | | | | | is added. This field is recorded in visit_database. So far, it can tell imported, synchronized, entension added or other(mainly testing) entries from user browsed entries. In the future, history extension API may allow queries to combinate with this criterion. BUG=none TEST=Unit tests are already included. Please test the web browser with history from previous versions to make sure the migration could be done properly. Also try to import or sync some history and inspect the sources added to the visit_source table in hitory database are correct. Original review=http://codereview.chromium.org/2906004/show Patch by weili@google.com TBR=brettw@chromium.org git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56754 0039d316-1c4b-4281-b951-d872f2087c98
* A new field to describe the sources of history urls(visits) is added. This ↵brettw@chromium.org2010-08-192-3/+6
| | | | | | | | | | | | | | | | | field is recorded in visit_database. So far, it can tell imported, synchronized, entension added or other(mainly testing) entries from user browsed entries. In the future, history extension API may allow queries to combinate with this criterion. BUG=none TEST=Unit tests are already included. Please test the web browser with history from previous versions to make sure the migration could be done properly. Also try to import or sync some history and inspect the sources added to the visit_source table in hitory database are correct. Original review=http://codereview.chromium.org/2906004/show Patch by weili@google.com git-svn-id: svn://svn.chromium.org/chrome/trunk/src@56742 0039d316-1c4b-4281-b951-d872f2087c98
* `#pragma once` for app, base, chrome, gfx, ipc, net, skia, viewsthakis@chromium.org2010-07-261-0/+1
| | | | | | | | | BUG=50273 TEST=everything still builds, build is 10% faster on windows, same speed on mac/linux TBR: erg git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53716 0039d316-1c4b-4281-b951-d872f2087c98
* Coverity: Fix a collection of uninitialized member variables, mostly in ↵finnur@chromium.org2010-07-231-1/+5
| | | | | | | | | | | | | | | | | | | | | extensions code, but some random ones outside extensions code as well. dhollowa : issue 11558: render_view_host.cc rafaelw : issue 11055: extension_browser_event_router.cc mirandac : issue 9443: profile_import_thread.cc estade : issue 9321: info_bubble_gtk.cc phajdan.jr: issue 8308: extensions_service_unittest.cc phajdan.jr: issue 8309: extensions_service_unittest.cc asargent : issue 8307: extension_browsertest.cc asargent : issue 7610: extension_browser_actions_api.h rafaelw : issue 2289: extension_function.cc BUG=None (Coverity issue id listed above) TEST=None Review URL: http://codereview.chromium.org/2832070 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@53451 0039d316-1c4b-4281-b951-d872f2087c98
* Coverity: Fix ProfileImportThread::OnImportStart dereferencing importer_ ↵mattm@chromium.org2010-07-151-4/+4
| | | | | | | | | | | | before null check. CID=9433 TEST=none BUG=none Review URL: http://codereview.chromium.org/2943012 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@52419 0039d316-1c4b-4281-b951-d872f2087c98
* Rename Chrome threads to use a "Cr" prefix.evan@chromium.org2010-06-091-3/+1
| | | | | | | | | | | Before we carefully used the app (Chrome/Chromium) name, but: 1) these are for internal debugging use only, so why compute this name 2) on Linux the thread ids are limited to 16 characters, and "Chromium" is too long Review URL: http://codereview.chromium.org/2741003 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@49296 0039d316-1c4b-4281-b951-d872f2087c98
* Move import in Mac OS X into its own process.mirandac@chromium.org2010-06-043-9/+251
| | | | | | | | BUG=18774 TEST=import still works. Review URL: http://codereview.chromium.org/502045 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@48928 0039d316-1c4b-4281-b951-d872f2087c98
* Make SystemMonitor not a Singleton and move it out of basephajdan.jr@chromium.org2009-11-261-1/+0
| | | | | | | | | | | | | SystemMonitor makes an assumption that through its lifetime a MessageLoop exists and stays the same. It is difficult and error-prone to satisfy that when it is a Singleton. It has caused problems in the past. Additionally, extract HighResoltionTimerManager out of time_win.cc, eliminating yet another Singleton. TEST=none BUG=none Review URL: http://codereview.chromium.org/431008 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@33214 0039d316-1c4b-4281-b951-d872f2087c98
* Add Profile Import Process Type.jeremy@chromium.org2009-09-173-0/+78
This is currently only used on OS X. We need a separate process to do profile import for 3 reasons: 1)In Firefox we load external libraries which we have no control over. 2)Conceptually it's safer to run parsing code OOP. 3)quoth chrome/browser/importer/nss_decryptor_mac.mm : """ On OS X the nss3 libraries are compiled with depedencies on one another, referenced using dyld's @executable_path directive. To make a long story short in order to get the libraries to load, dyld's fallback path needs to be set to the directory containing the libraries. To do so, the process this function runs in must have the DYLD_FALLBACK_LIBRARY_PATH set on startup to said directory. """ BUG=14458 TEST=None Possible Review URL: http://codereview.chromium.org/193131 git-svn-id: svn://svn.chromium.org/chrome/trunk/src@26501 0039d316-1c4b-4281-b951-d872f2087c98
generated by cgit v1.1 at 2025-02-15 17:26:41 +0000