-
Notifications
You must be signed in to change notification settings - Fork 675
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
Added support for renameat2 on linux #1458
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can you please remove formatting changes from the PR?
Of course, yes. Done. |
…for any cross-compile targets, as per comment here: nix-rust#1458 (comment)
Ok, it looks good. Would you mind squashing your commits, and rebasing to fix the CHANGELOG? |
5c3f183
to
80b1f28
Compare
Thank you @asomers . That's done now, and everything looks clean! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
bors r+
c870dde
to
1a23312
Compare
Canceled. |
Apols. I squashed my commits in to one again and interrupted this. |
bors retry |
Hi, please find my PR for adding the linux-specific
renameat2
syscall. It's largely similar torenameat
, with an additional flags parameter:The flags are:
PLEASE NOTE: It looks like my formatter has made numerous changes. If you have a preferred formatting config then please let me know, and I can push up changes consistent with the accepted style.
I'm not all that experienced with rust, and this is my first time looking at the nix project, so I'm more than happy to receive guidance on improving my submission.
Cheers!