Re: [PATCH] tests: copy.c destination permissions lost when backup specified

[Eric Blake]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

According to Jim Meyering on 3/30/2009 6:14 AM:
>> I give great value for backups, but still I would like to see new and
>> old destination files to have same permissions. Of course when
>> --preserve is specified expectation is changed; source permission
>> should appear for the new file.
>>
>> Am I only one thinking this way?
> 
> Perhaps.
> In any case, this behavior dates back to the invention of the --backup
> option over 17 years ago.
> 
> Sorry, but I see no reason to change it.

There is no reason to change the semantics of an existing option.
However, there has been list discussion of adding an option to cp that
will preserve as many attributes as possible (better than what you
currently get with 'touch --reference'); perhaps if that new option is
ever written, it can be used in concert with --backup to get the semantics
you want?

- --
Don't work too hard, make some time for fun as well!

Eric Blake             address@hidden
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (Cygwin)
Comment: Public key at home.comcast.net/~ericblake/eblake.gpg
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iEYEARECAAYFAknQuM8ACgkQ84KuGfSFAYDxqQCfdwVgFkBQ6ZMUuW+9C6lboQPG
ZUsAoK0F0g/GJZWG2+6RimG2cKBjHMMv
=C8yR
-----END PGP SIGNATURE-----