From 16e96b1242d15be04d34dac3a1081a222256247e Mon Sep 17 00:00:00 2001
From: Dhruba Borthakur <dhruba@fb.com>
Date: Fri, 25 Jan 2013 09:10:26 -0800
Subject: [PATCH] Cleanup TODO/NEWS/AUTHORS files

Summary:
These files are not relevant anymore.

Test Plan:

Reviewers:

CC:

Task ID: #

Blame Rev:
---
 AUTHORS           |  8 --------
 NEWS              | 17 -----------------
 TODO              | 13 -------------
 fbcode.clang31.sh |  1 -
 fbcode.gcc471.sh  |  1 -
 5 files changed, 40 deletions(-)
 delete mode 100644 AUTHORS
 delete mode 100644 NEWS
 delete mode 100644 TODO

diff --git a/AUTHORS b/AUTHORS
deleted file mode 100644
index 27a9407e5..000000000
--- a/AUTHORS
+++ /dev/null
@@ -1,8 +0,0 @@
-# Names should be added to this file like so:
-# Name or Organization <email address>
-
-Google Inc.
-
-# Initial version authors:
-Jeffrey Dean <jeff@google.com>
-Sanjay Ghemawat <sanjay@google.com>
diff --git a/NEWS b/NEWS
deleted file mode 100644
index 3fd99242d..000000000
--- a/NEWS
+++ /dev/null
@@ -1,17 +0,0 @@
-Release 1.2 2011-05-16
-----------------------
-
-Fixes for larger databases (tested up to one billion 100-byte entries,
-i.e., ~100GB).
-
-(1) Place hard limit on number of level-0 files.  This fixes errors
-of the form "too many open files".
-
-(2) Fixed memtable management.  Before the fix, a heavy write burst
-could cause unbounded memory usage.
-
-A fix for a logging bug where the reader would incorrectly complain
-about corruption.
-
-Allow public access to WriteBatch contents so that users can easily
-wrap a DB.
diff --git a/TODO b/TODO
deleted file mode 100644
index 9130b6a9f..000000000
--- a/TODO
+++ /dev/null
@@ -1,13 +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.
-
-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?
diff --git a/fbcode.clang31.sh b/fbcode.clang31.sh
index 276bf12ca..bcedad200 100644
--- a/fbcode.clang31.sh
+++ b/fbcode.clang31.sh
@@ -3,7 +3,6 @@
 # Set environment variables so that we can compile leveldb using
 # fbcode settings.  It uses the latest g++ compiler and also
 # uses jemalloc
-# This is compiled with gcc version 4.7.1 for zeus proxy
 
 TOOLCHAIN_REV=f365dbeae46a30414a2874a6f45e73e10f1caf7d
 TOOLCHAIN_EXECUTABLES="/mnt/gvfs/third-party/$TOOLCHAIN_REV/centos5.2-native"
diff --git a/fbcode.gcc471.sh b/fbcode.gcc471.sh
index 1736a18f5..c6d94eb23 100644
--- a/fbcode.gcc471.sh
+++ b/fbcode.gcc471.sh
@@ -3,7 +3,6 @@
 # Set environment variables so that we can compile leveldb using
 # fbcode settings.  It uses the latest g++ compiler and also
 # uses jemalloc
-# This is compiled with gcc version 4.7.1 for zeus proxy
 
 TOOLCHAIN_REV=20d3328ac30f633840ce819ad03019f415267a86
 TOOLCHAIN_EXECUTABLES="/mnt/gvfs/third-party/$TOOLCHAIN_REV/centos5.2-native"