| Message ID | 1436787388-24414-1-git-send-email-arnout@mind.be |
|---|---|
| State | Accepted |
| Headers | show |
Hi Arnout, On Mon, Jul 13, 2015 at 01:36:28PM +0200, Arnout Vandecappelle (Essensium/Mind) wrote: > Since the rsync of skeleton or rootfs now changes the permissions of > the copied files and directories, this may break existing setups that > rely on these permissions being kept. So add a release not explaining note > how it should be done. baruch
Dear Arnout Vandecappelle (Essensium/Mind), On Mon, 13 Jul 2015 13:36:28 +0200, Arnout Vandecappelle (Essensium/Mind) wrote: > Since the rsync of skeleton or rootfs now changes the permissions of > the copied files and directories, this may break existing setups that > rely on these permissions being kept. So add a release not explaining > how it should be done. > > Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> > --- > CHANGES | 11 +++++++++++ > 1 file changed, 11 insertions(+) I've fixed the commit log as suggested by Baruch and applied, thanks! Thomas
diff --git a/CHANGES b/CHANGES index 3f5162e..1e94929 100644 --- a/CHANGES +++ b/CHANGES @@ -1,3 +1,14 @@ +2015.08-rc1, not yet released + + Fixes all over the tree and new features. + + Infrastructure: Buildroot takes better care now of generating + predictable permissions in the target filesystem. However, + existing permissions on a custom skeleton or rootfs overlay + will no longer be preserved. Therefore, it is necessary to + add a permission table (BR2_ROOTFS_DEVICE_TABLE) to set + the required permissions. + 2015.05, Released May 31st, 2015 Minor fixes.
Since the rsync of skeleton or rootfs now changes the permissions of the copied files and directories, this may break existing setups that rely on these permissions being kept. So add a release not explaining how it should be done. Signed-off-by: Arnout Vandecappelle (Essensium/Mind) <arnout@mind.be> --- CHANGES | 11 +++++++++++ 1 file changed, 11 insertions(+)