Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

CP-50298: Support restoring dir to specified mode and user/group #187

Open
wants to merge 1 commit into
base: release/xs8
Choose a base branch
from

Conversation

DeliZhangX
Copy link
Contributor

attributes

Signed-off-by: Deli Zhang [email protected]
(cherry picked from commit 0ccfe46)

attributes

Signed-off-by: Deli Zhang <[email protected]>
(cherry picked from commit 0ccfe46)
@DeliZhangX
Copy link
Contributor Author

Will merge in PI26

upgrade.py Show resolved Hide resolved
def copy_ownership(src_root, src_path, dst_root, dst_path):
# Copy attributes from a path in a source root to another path in a
# destination root.
# - The ownership is copied such that it is notaffected by changes
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

typo: notaffected -> not affected

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will fix.

# destination root.
# - The ownership is copied such that it is notaffected by changes
# in the underlying uid/gid. Or it's set to the specified.
# - The mode is set to the specified.
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not an English native speaker but I think specified needs something after like specified one. I would change to The mode is set to the specified one if present.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will fix.

@DeliZhangX
Copy link
Contributor Author

I cannot push fix code. Can admin give me feature/openssl3 branch write permission?

@freddy77
Copy link
Collaborator

I cannot push fix code. Can admin give me feature/openssl3 branch write permission?

You should not use feature/ branch, I would suggest to create another repo/branch instead (and open the PR again).

@DeliZhangX
Copy link
Contributor Author

I cannot push fix code. Can admin give me feature/openssl3 branch write permission?

You should not use feature/ branch, I would suggest to create another repo/branch instead (and open the PR again).

This change was already reviewed before #170 (#168) from private to feature. Now to merge to target release/xs8 from feature.

@GeraldEV
Copy link
Collaborator

I cannot push fix code. Can admin give me feature/openssl3 branch write permission?

You should not use feature/ branch, I would suggest to create another repo/branch instead (and open the PR again).

This change was already reviewed before #170 (#168) from private to feature. Now to merge to target release/xs8 from feature.

You'll need to open a PR to the feature branch, once merged that will update this PR
In principle the PRs should all be reviewed on their way into the feature branch so w know everything in a feature branch has already been reviewed (otherwise someone might sneak some extra commits in under the radar before it's merged to master)

@DeliZhangX
Copy link
Contributor Author

Fixed in PR #191

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants