rsync - Jul 2005 - change in backup behavior from 2.5 to 2.6

In rsync 2.5, using the --backup and --backup-dir switches without a
--suffix would copy backed up files to the backup dir with no extension.
 In 2.6, you must use a blank suffix ("suffix=") in order to get the
same behavior.  This means that 2.5 clients are unable to backup to the
server without putting a suffix on the backups.  The documentation also
still indicates that the old behavior would be expected.  Can someone
clarify which is the current correct behavior, and if the new
methodology is correct, can the documentation be changed?

On Fri, Jul 15, 2005 at 12:15:41PM -0600, Larry Bernstone
wrote:
> In rsync 2.5, using the --backup and --backup-dir switches without a
> --suffix would copy backed up files to the backup dir with no extension.
This is true in all versions of rsync (that I know of), including all
2.6.x versions.
>  In 2.6, you must use a blank suffix ("suffix=") in order to get
the
> same behavior.
I've never seen that happen.  Are you using a modified rsync from
someone who has broken this?  I do know that if you manually specify
--suffix= to a 2.5.x rsync that it would fail to pass the option in a
way that would survive the remote-shell invocation (and this has been
fixed in the 2.6.x series), but you don't need to specify
--suffix=''
when you're using --backup-dir.

..wayne..