From: Nick Mathewson Date: Wed, 18 Jul 2012 14:24:17 +0000 (-0400) Subject: Have the bug6252 commit message reflect its on-again/off-again status X-Git-Tag: tor-0.2.3.21-rc~6^2~16^2 X-Git-Url: http://git.ipfire.org/gitweb.cgi?a=commitdiff_plain;h=393944dfb67fb27991e152ec67f74cebbf3a23ba;p=thirdparty%2Ftor.git 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 0d29203fab..f7fd00cb38 100644 --- 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. +