Have the bug6252 commit message reflect its on-again/off-again status

diff --git a/changes/bug6252 b/changes/bug6252_again
similarity index 65%
rename from changes/bug6252
rename to changes/bug6252_again
index 0d29203fabbfc6fcba61ba6d59d6f3391b848929..f7fd00cb3858bb6cd3674b48f5b1e904dff9f1f3 100644 (file)
--- a/changes/bug6252
+++ b/changes/bug6252_again
@@ -4,5 +4,8 @@
       than our flow control would have allowed, or to gum up the network,
       or possibly to do targeted memory denial-of-service attacks on
       entry nodes. Fixes bug 6252. Bugfix on the 54th commit on Tor --
-      from July 2002, before the release of Tor 0.0.0.
+      from July 2002, before the release of Tor 0.0.0.  We had committed
+      this patch previously, but we had to revert it because of bug 6271.
+      Now that 6271 is fixed, this appears to work.
+