From c80df20095112b2133553258d1d093747a6b2358 Mon Sep 17 00:00:00 2001 From: Roger Dingledine Date: Thu, 7 Jul 2011 13:35:26 -0400 Subject: [PATCH] remove changes file i'd already merged in (oops) --- changes/bug3465-022 | 6 ------ changes/cid_428 | 5 ----- changes/cid_450 | 5 ----- changes/memleak_rendcache | 4 ---- 4 files changed, 20 deletions(-) delete mode 100644 changes/bug3465-022 delete mode 100644 changes/cid_428 delete mode 100644 changes/cid_450 delete mode 100644 changes/memleak_rendcache diff --git a/changes/bug3465-022 b/changes/bug3465-022 deleted file mode 100644 index 2d226162aa..0000000000 --- a/changes/bug3465-022 +++ /dev/null @@ -1,6 +0,0 @@ - o Minor bugfixes: - - - Add BUILDTIMEOUT_SET to the list returned by the 'GETINFO - events/names' control-port command. Bugfix on 0.2.2.9-alpha; - fixes part of bug 3465. - diff --git a/changes/cid_428 b/changes/cid_428 deleted file mode 100644 index cb0fc8c2b2..0000000000 --- a/changes/cid_428 +++ /dev/null @@ -1,5 +0,0 @@ - o Minor bugfixes: - - Always NUL-terminate the sun_path field of a sockaddr_un before - passing it to the kernel. (Not a security issue: kernels are - smart enough to reject bad sockaddr_uns.) Found by Coverity; CID - # 428. Bugfix on Tor 0.2.0.3-alpha. diff --git a/changes/cid_450 b/changes/cid_450 deleted file mode 100644 index 2045fca239..0000000000 --- a/changes/cid_450 +++ /dev/null @@ -1,5 +0,0 @@ - o Minor bugfixes: - - Don't stack-allocate the list of supplementary GIDs when we're - about to log them. Stack-allocating NGROUPS_MAX gid_t elements - could take up to 256K, which is way too much stack. Found by - Coverity; CID #450. Bugfix on 0.2.1.7-alpha. diff --git a/changes/memleak_rendcache b/changes/memleak_rendcache deleted file mode 100644 index 93b1f6141b..0000000000 --- a/changes/memleak_rendcache +++ /dev/null @@ -1,4 +0,0 @@ - o Minor bugfixes: - - Fix a memory leak when receiving a descriptor for a hidden - service we didn't ask for. Found by Coverity; CID#30. Bugfix on - 0.2.2.26-beta. -- 2.47.3