[tor-commits] [tor/release-0.2.2] fold in the latest changes file.

[arma at torproject.org]

commit 2bdf8102cd6ebde3c93f23a89336b9c1845651d6
Author: Roger Dingledine <arma at torproject.org>
Date:   Sat May 21 18:27:02 2011 -0400

    fold in the latest changes file.
    
    schedule another release for this coming week
---
 ChangeLog       |   13 +++++++++++++
 changes/bug1810 |    6 ------
 changes/bug3252 |    4 ----
 3 files changed, 13 insertions(+), 10 deletions(-)

diff --git a/ChangeLog b/ChangeLog
index 79148e1..92478b3 100644
--- a/ChangeLog
+++ b/ChangeLog
@@ -1,3 +1,16 @@
+Changes in version 0.2.2.28-beta - 2011-05-2?
+  o Major bugfixes:
+    - Don't decide to make a new descriptor when receiving a HUP signal.
+      This bug has caused a lot of 0.2.2.x relays to disappear from the
+      consensus periodically. Fixes the most common case of triggering
+      bug 1810; bugfix on 0.2.2.7-alpha.
+
+  o Minor features:
+    - Relays now log the reason for publishing a new relay descriptor,
+      so we have a better chance of hunting down the root cause of bug
+      1810. Resolves ticket 3252.
+
+
 Changes in version 0.2.2.27-beta - 2011-05-18
   Tor 0.2.2.27-beta fixes a bridge-related stability bug in the previous
   release, and also adds a few more general bugfixes.
diff --git a/changes/bug1810 b/changes/bug1810
deleted file mode 100644
index 11e561f..0000000
--- a/changes/bug1810
+++ /dev/null
@@ -1,6 +0,0 @@
-  o Major bugfixes:
-    - Don't decide to make a new descriptor when receiving a HUP signal.
-      This bug has caused a lot of relays to disappear from the consensus
-      periodically. Fixes the most common case of triggering bug 1810;
-      bugfix on 0.2.2.7-alpha.
-
diff --git a/changes/bug3252 b/changes/bug3252
deleted file mode 100644
index f85f633..0000000
--- a/changes/bug3252
+++ /dev/null
@@ -1,4 +0,0 @@
-  o Minor features:
-    - Relays now log the reason for publishing a new relay descriptor,
-      so we have a better chance of hunting down the root cause of bug
-      1810. Resolves ticket 3252.