1* TODO file for GNU sharutils 2 3Tell <drepper@gnu.ai.mit.edu> if you feel like volunteering for any 4of these ideas, listed more or less in decreasing order of priority. 5Some TODO items are implicit from received email. See file BACKLOG. 6 7(One more word. This list already existed when I took over the task 8of maintaining sharutils. I have not investigated the list enough 9to say this will also be correct for me. But Franc,ois and I often 10agree so it is likely.) 11 12 13.# Next release 14The next release will have these changes: 15. + better integrate uucode with the others, code-wise 16 17 18.@ ChangeLog 19 20.* Short term 21. + Utiliser guillemets fran�ais dans fr.tt 22. + convert uucode documentation into sharutils.texi 23. + remove many fixed limits, everywhere 24. + delete useless code, among which some matching features 25. + simplify further `:' vs `true' usage, the latter might be avoided 26. + remsync matters 27. - documentation 28The documentation is still rudimentary, but might help you to 29understand what is going on. Many examples in some quick start 30node might help. In any case, criticize it at will, and let me 31use your comments as an incentive for further improvement. Any help 32from native English speakers is appreciated. 33 34Carefully ensure that you have a backup of your synchronized trees 35before your tries of remsync. It does work for me, but who knows if 36it will not be dangerous in your particular setup. 37 38White lines, and lines beginning with \`#\', are comments. Command 39keywords may be abbreviated to their first letter. Space between 40successive keywords may be omitted. Variable arguments may often be 41replaced by numeric index from lists. SITE may also be local or 0. 42SITE_SET is a list of SITE, default is all. A ! prefix complements it. 43The following commands are meant for automatic internal use: 44. - handle receving files over symbolic links or directories 45. - maintain a project title 46. - no remote could also be local 47. - diagnose /net/mnt_tmp/... directories 48. - if deleting a scan, already registered files declared unexisting 49. - have a paranoid option, in which diffs are always done 50. - study if and how the symbolic links might be transported 51 52.* Medium term 53. + integrate remsync script and documentation 54. + have -C as synonymous for -d in shar 55 1994-08-22, Karl Berry <kb@cs.umb.edu> 56. + speedup unshar, far too slow while matching sed input 57. + construct some `make check' for shar/unshar 58. + do something sensible with file permissions 59. + study if the symbolic links might be transported 60. + when local/remote directories are relative, this should be to ~user 61. + do not send absolute files 62. + add some `-h UNSHAR.HDR' option 63 1994-08-19, Marty Leisner <leisner@sdsp.mc.xerox.com> 64. + decode options from a SHAR environment variable 65 1994-08-30, Ulrich Drepper <drepper@ira.uka.de> 66. + remsync matters 67. - have a command to rename a remote while keeping all its values 68. - do something sensible with file permissions 69. - qualify each scan with destination sites 70. - emacslisp/menage.el to omit, have it reconstructed automatically instead 71. - have an equivalence system for email addresses 72. - avoid computing checksums for ignored files 73. - have a master directory for .remsync's, have them located elsewhere 74. - have a recursive mode finding all .remsync's in tree 75. - provide encryption hooks, so people can use e.g. PGP or rot13 :-) 76 77.* Long term 78. + automatically retrieve in correct sequence from a bunched file 79 1994-08-24, Karl Berry <kb@cs.umb.edu> 80. + when -T, just reject binary files 81 1994-08-29, Andrew A. Chernov <ache@astral.msk.su> 82 1994-09-11, Eric Backus <ericb@lsid.hp.com> -- disagrees 83