Use umask kluge from rsync.fns to try to get rid of a potential
[rsync/rsync.git] / NEWS
CommitLineData
8fe27e76 1NEWS for rsync 2.6.6 (UNRELEASED)
3ae6c187 2Protocol: 29 (unchanged)
8fe27e76 3Changes since 2.6.5:
060f3150 4
ac1541f4
WD
5 BUG FIXES:
6
8fe27e76
WD
7 - The outputting of hard-linked files when verbosity was > 1 was not right:
8 without -i it would output the name of each hard-linked file as thought
9 it had been changed (it now outputs a "is hard linked" message for the
10 file); with -i it would could output all trailing dots for an unchanged
11 hard-link (it now changes those dots to spaces, as is done for other
12 unchanged files).
bac72590 13
ac1541f4
WD
14 ENHANCEMENTS:
15
8fe27e76
WD
16 - Made the "max verbosity" setting in the rsyncd.conf file settable on a
17 per-module basis (which now matches the documentation).
7d7a34ae 18
ac1541f4
WD
19 BUILD CHANGES:
20
8fe27e76
WD
21 - Made configure define NOBODY_USER (currently hard-wired to "nobody") and
22 NOBODY_GROUP (set to either "nobody" or "nogroup" depending on what we
23 find in the /etc/group file).
7d7a34ae 24
8fe27e76
WD
25 - Added a test to the test suite, itemized.test, that tests the output of
26 -i (log-format w/%i) and some double-verbose messages.