X-Git-Url: https://mattmccutchen.net/rsync/rsync.git/blobdiff_plain/5ba268efa84e16fde582f5d168f938917b25bac4..8bd1a73e14bc1efb9bab01fbd1d693725183cca3:/TODO

diff --git a/TODO b/TODO
index e035e6c6..704e5793 100644
--- a/TODO
+++ b/TODO
@@ -2,6 +2,13 @@
 
 BUGS ---------------------------------------------------------------
 
+rsync-url barfs on upload
+
+  rsync foo rsync://localhost/transfer/
+
+  Fix the parser.
+
+
 There seems to be a bug with hardlinks
 
   mbp/2 build$ ls -l /tmp/a /tmp/b -i
@@ -106,6 +113,15 @@ Cross-test versions
   some testing and also be the most common case for having different
   versions and not being able to upgrade.
 
+--no-blocking-io might be broken
+
+  in the same way as --no-whole-file; somebody needs to check.
+
+Do not rely on having a group called "nobody"
+
+  http://www.linuxbase.org/spec/refspecs/LSB_1.1.0/gLSB/usernames.html
+
+  On Debian it's "nogroup"
 
 DAEMON --------------------------------------------------------------
 
@@ -297,6 +313,15 @@ Hard-link handling
 
 IPv6
 
+  Put back the old socket code; if on a machine that does not properly
+  support the getaddrinfo API, then use it.  This is probably much
+  simpler than reimplementing it.  This might get us working again on
+  RedHat 5 and similar systems.  Although the Kame patch seems like a
+  good idea, in fact it is a much broader interface than the
+  relatively narrow "open by name", "accept and log" interface that
+  rsync uses internally, and it has the disadvantage of clashing with
+  half-arsed implementations of the API.
+
   Implement suggestions from http://www.kame.net/newsletter/19980604/
   and ftp://ftp.iij.ad.jp/pub/RFC/rfc2553.txt
 
@@ -476,6 +501,8 @@ chmod:
   the program.  For bonus points there would be a test case for the  
   parser.
 
+  Possibly also --chown
+
   (Debian #23628)
 
 
@@ -642,6 +669,12 @@ Versions of read() and write() that corrupt the stream, or abruptly fail
 Separate makefile target to run rough tests -- or perhaps just run
 them every time?
 
+Test "refuse options" works
+
+  What about for --recursive?
+
+  If you specify an unrecognized option here, you should get an error.
+
 
 DOCUMENTATION --------------------------------------------------------