From: Anand Jain <anand.jain@oracle.com>
To: Peter Kjellerstedt <peter.kjellerstedt@axis.com>,
linux-btrfs@vger.kernel.org
Cc: pkj@axis.com
Subject: Re: [PATCH] btrfs-progs: build: Do not use cp -a to install files
Date: Thu, 5 Apr 2018 14:35:18 +0800 [thread overview]
Message-ID: <30cee140-7ffd-9461-2c4c-b26d11b6eb20@oracle.com> (raw)
In-Reply-To: <20180404140459.20644-1-pkj@axis.com>
On 04/04/2018 10:04 PM, Peter Kjellerstedt wrote:
> Using cp -a to install files will preserve the ownership of the
> original files (if possible), which is typically not wanted. E.g., if
> the files were built by a normal user, but are being installed by
> root, then the installed files would maintain the UIDs/GIDs of the
> user that built the files rather than be owned by root.
Reviewed-by: Anand Jain <anand.jain@oracle.com>
Thanks, Anand
next prev parent reply other threads:[~2018-04-05 6:33 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-04-04 14:04 [PATCH] btrfs-progs: build: Do not use cp -a to install files Peter Kjellerstedt
2018-04-05 6:35 ` Anand Jain [this message]
2018-04-06 12:55 ` David Sterba
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=30cee140-7ffd-9461-2c4c-b26d11b6eb20@oracle.com \
--to=anand.jain@oracle.com \
--cc=linux-btrfs@vger.kernel.org \
--cc=peter.kjellerstedt@axis.com \
--cc=pkj@axis.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox