-NEWS for rsync 2.6.6 (UNRELEASED)
-Protocol: 29 (unchanged)
-Changes since 2.6.5:
+NEWS for rsync 3.0.1 (UNRELEASED)
+Protocol: 30 (unchanged)
+Changes since 3.0.0:
BUG FIXES:
- - The setting of flist->high in clean_flist() was wrong for an empty list.
- This could cause flist_find() to crash in certain rare circumstances
- (e.g. if just the right directory setup was around when --fuzzy was
- combined with --list-dest).
-
- - The outputting of hard-linked files when verbosity was > 1 was not right:
- without -i it would output the name of each hard-linked file as thought
- it had been changed (it now outputs a "is hard linked" message for the
- file); with -i it would could output all trailing dots for an unchanged
- hard-link (it now changes those dots to spaces, as is done for other
- unchanged files).
-
- - When backing up a changed symlink or device, get rid of any old backup
- item so that we don't get an already-exists error.
+ - ...
ENHANCEMENTS:
- - Made the "max verbosity" setting in the rsyncd.conf file settable on a
- per-module basis (which now matches the documentation).
-
- - The support/rrsync script has been upgraded to verify the args of options
- that take them (instead of rejecting any such options). The scrip was
- also changed to try to be more secure and to fix a problem in the parsing
- of a copy that has multiple sources.
+ - ...
- BUILD CHANGES:
+ INTERNAL:
- - Made configure define NOBODY_USER (currently hard-wired to "nobody") and
- NOBODY_GROUP (set to either "nobody" or "nogroup" depending on what we
- find in the /etc/group file).
+ - ...
- - Added a test to the test suite, itemized.test, that tests the output of
- -i (log-format w/%i) and some double-verbose messages.
+ DEVELOPER RELATED:
+ - ...