improve handling of @@line continuations

[privoxy.git] / TODO

diff --git a/TODO b/TODO
index bdd8896..49da6ad 100644 (file)
--- a/TODO
+++ b/TODO
@@ -1,14 +1,12 @@
-$Id: TODO,v 1.163 2017/05/20 09:25:14 fabiankeil Exp $
-
 Some Privoxy-related tasks, sorted by the time they
 have been added, not by priority.
 
 The latest version should be available at:
-http://ijbswa.cvs.sourceforge.net/viewvc/ijbswa/current/TODO
+https://www.privoxy.org/gitweb/?p=privoxy.git;a=blob_plain;f=TODO;hb=HEAD
 
 There's work in progress to fund development on these items using
 donations. If you want to donate, please have a look at:
-http://www.privoxy.org/faq/general.html#DONATE
+https://www.privoxy.org/faq/general.html#DONATE
 
 1)  Add more regression tests. Filters should be tested automatically
     (variables too). Could probably reuse large parts of Privoxy-Filter-Test.
@@ -348,7 +346,7 @@ http://www.privoxy.org/faq/general.html#DONATE
      running out of stack space, causing the kernel to kill Privoxy
      ungracefully.
 
-121) Add HTTP/2 support. As a first step, incomming HTTP/1.x requests
+121) Add HTTP/2 support. As a first step, incoming HTTP/1.x requests
      should be translated to outgoing HTTP/2 requests where possible
      (and if desired by the user).
      Interested donors: 1.
@@ -439,9 +437,6 @@ http://www.privoxy.org/faq/general.html#DONATE
      currently can result in client requests to config.privoxy.org on the
      Internet which may not be desirable.
 
-149) Use poll() for socket selection so the number of sockets Privoxy
-     can deal with isn't limited to FD_SETSIZE anymore.
-
 150) Add blacklistd support.
 
 151) Let the dok-tidy target work cross-platform without introducing
@@ -469,8 +464,6 @@ http://www.privoxy.org/faq/general.html#DONATE
      to the one used for ftp. Motivation:
      https://lists.privoxy.org/pipermail/privoxy-users/2017-March/000195.html
 
-157) Add a directive to control the currently hardcoded receive-buffer size.
-
 158) Use a single thread to wait for new requests on reused client connections.
      Currently the thread that handles the first request on a connection
      stays responsible for the client connect until it gets closed.