[Author Prev][Author Next][Thread Prev][Thread Next][Author Index][Thread Index]
[tor-commits] [tor/release-0.3.1] Lintchanges fix: bug numbers do not get #d, but they do get "fix on"
commit ac89262b1c37e86b2b57b9b1642f6db48fde0808
Author: Nick Mathewson <nickm@xxxxxxxxxxxxxx>
Date: Thu Jun 29 15:49:32 2017 -0400
Lintchanges fix: bug numbers do not get #d, but they do get "fix on"
---
changes/bug22212 | 3 ++-
1 file changed, 2 insertions(+), 1 deletion(-)
diff --git a/changes/bug22212 b/changes/bug22212
index f92d670..dc1604a 100644
--- a/changes/bug22212
+++ b/changes/bug22212
@@ -2,4 +2,5 @@
- Demote a warn that was caused by libevent delays to info if
the padding is less than 4.5 seconds late, or notice if it is more
(4.5 seconds is the amount of time that a netflow record might
- be emitted after, if we chose the maximum timeout). Fixes bug #22212.
+ be emitted after, if we chose the maximum timeout). Fixes bug 22212;
+ bugfix on 0.3.1.1-alpha.
_______________________________________________
tor-commits mailing list
tor-commits@xxxxxxxxxxxxxxxxxxxx
https://lists.torproject.org/cgi-bin/mailman/listinfo/tor-commits