From 3725179736e2b5372664163470e7ef3dc76529a4 Mon Sep 17 00:00:00 2001
From: Sfan5 <sfan5@live.de>
Date: Mon, 9 Sep 2013 22:46:18 +0200
Subject: Use system-wide LevelDB instead of bundled one

---
 src/leveldb/TODO | 14 --------------
 1 file changed, 14 deletions(-)
 delete mode 100644 src/leveldb/TODO

(limited to 'src/leveldb/TODO')

diff --git a/src/leveldb/TODO b/src/leveldb/TODO
deleted file mode 100644
index e603c0713..000000000
--- a/src/leveldb/TODO
+++ /dev/null
@@ -1,14 +0,0 @@
-ss
-- Stats
-
-db
-- Maybe implement DB::BulkDeleteForRange(start_key, end_key)
-  that would blow away files whose ranges are entirely contained
-  within [start_key..end_key]?  For Chrome, deletion of obsolete
-  object stores, etc. can be done in the background anyway, so
-  probably not that important.
-- There have been requests for MultiGet.
-
-After a range is completely deleted, what gets rid of the
-corresponding files if we do no future changes to that range.  Make
-the conditions for triggering compactions fire in more situations?
-- 
cgit v1.2.3