If the --partial-dir value is an absolute path and we use a file in

[rsync/rsync.git] / NEWS

diff --git a/NEWS b/NEWS
index fd5a890..f477712 100644 (file)
--- a/NEWS
+++ b/NEWS
@@ -5,24 +5,24 @@ Changes since 2.6.8:
   BUG FIXES:
 
     - An rsync daemon that is receiving files with "use chroot = no" no longer
   BUG FIXES:
 
     - An rsync daemon that is receiving files with "use chroot = no" no longer

-      sanitizes the symlink target strings.  This means that the symlinks
-      values will now be accepted (and returned) with all their symlink info
+      sanitizes the symlink target strings.  This means that each symlink's
+      value will now be accepted (and thus returned) with its symlink info

       intact.  Also, in order to keep things safe, any option that tells a
       non-chroot daemon to treat some symlinks as their referent (such as
       --copy-links or --keep-dirlinks) now manually checks the symlink chain
       to ensure that the symlinks do not try to escape past the top of the
       intact.  Also, in order to keep things safe, any option that tells a
       non-chroot daemon to treat some symlinks as their referent (such as
       --copy-links or --keep-dirlinks) now manually checks the symlink chain
       to ensure that the symlinks do not try to escape past the top of the

-      module's path.  This makes a non-chroot daemon behave the same as a
-      chroot daemon with regard to symlinks, and also avoids a potential
-      problem where pre-existing symlinks could have escaped the module's
-      hierarchy.
+      module's path.  Both these changes make a non-chroot daemon behave the
+      same as a chroot daemon with regard to symlinks, and also avoids a
+      potential problem where a pre-existing symlink could have escaped the
+      module's hierarchy.

 
     - Fixed a overzealous sanitizing bug in the handling of the --*-dest
 
     - Fixed a overzealous sanitizing bug in the handling of the --*-dest

-      options (--link-dest, --copy-dest, and --compare-dest):  if the copy's
+      options (--link-dest, --copy-dest, and --compare-dest): if the copy's

       destination dir is deeper than the top of the module's path, these
       options now accept a safe number of ../ (parent-dir) references (since
       these options are relative to the destination dir).  The old code
       incorrectly chopped off all "../" prefixes for these options, no matter
       destination dir is deeper than the top of the module's path, these
       options now accept a safe number of ../ (parent-dir) references (since
       these options are relative to the destination dir).  The old code
       incorrectly chopped off all "../" prefixes for these options, no matter

-      how deep the destination directory was in the hierarchy.
+      how deep the destination directory was in the module's hierarchy.

 
     - Fixed a bug where a deferred info/error/log message could get sent
       directly to the sender instead of being handled by rwrite() in the
 
     - Fixed a bug where a deferred info/error/log message could get sent
       directly to the sender instead of being handled by rwrite() in the


@@ -36,7 +36,9 @@ Changes since 2.6.8:
       or --size-only is specified.
 
     - The daemon now calls more timezone-using functions prior to doing a
       or --size-only is specified.
 
     - The daemon now calls more timezone-using functions prior to doing a

-      chroot.
+      chroot.  This should help some C libraries to generate proper timestamps
+      from inside a chrooted daemon (and to not try to access /etc/timezone
+      over and over again).

 
   ENHANCEMENTS:
 
 
   ENHANCEMENTS: