[sqlite] Bring patches up-to-date with trunk.

third_party/sqlite/README.chromium

 Name: sqlite
 URL: http://sqlite.org/
-Version: 3.8.7.4
+Version: 3.10.2
 Included In Release: Yes
 Security Critical: Yes
 License: Public domain
 
 1) Managing differences between SQLite core and Chromium's version.
 2) Making changes to Chromium SQLite.
 3) Import new release of SQLite.
 4) Running SQLite's test suite within the Chromium checkout.
 
 ---
@@ skipping 34 matching lines @@
 or OSX.  They may assume a modern version of git (I'm using 2.2.1).
 
 # Everything based in sqlite subdir.
 cd third_party/sqlite
 
 BASE=3080704
 
 #### Create a reference branch.
 git checkout -b sqlite_${BASE} master
 git rm -rf src
+rm -rf src  # In case there are things git doesn't know in there.
 cp -a sqlite-src-${BASE} src
 # -f includes ignored files, of which there are a couple.
 git add -f src/
 git commit -m "Reset to sqlite-src-${BASE}"
 # This branch is unlikely to build.
 
 #### Create a reference branch with patches applied.
 git checkout -b sqlite_${BASE}_patched master
 git rebase sqlite_${BASE}
 git am --keep-non-patch patches/*.patch
@@ skipping 182 matching lines @@
 NOTE(shess): On Ubuntu it is possible to run the tests in a tmpfs something
 like:
 
 TMPFS=/dev/shm/sqlite_build
 BUILD=$PWD
 mkdir $TMPFS
 (cd $TMPFS ; $BUILD/testfixture $BUILD/../test/veryquick.test >/tmp/test.log)
 
 This is faster, but it is plausible that different things are being tested than
 real-world use.