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

Revert "rsync: fix regression with _FORTIFY_SOURCE=2" #265876

Merged
merged 1 commit into from
Nov 6, 2023

Conversation

RaitoBezarius
Copy link
Member

Reverts #265846 — it should have gone to staging. We are cancelling evaluations, please resend the PR to staging.

@RaitoBezarius
Copy link
Member Author

FYI @ehmry.

@alyssais
Copy link
Member

alyssais commented Nov 6, 2023

Commit messages for reverts should always explain the reason for the revert. You can do this when you merge, using the "Squash and merge" option.

@RaitoBezarius
Copy link
Member Author

Commit messages for reverts should always explain the reason for the revert. You can do this when you merge, using the "Squash and merge" option.

Gotcha, thank you for reminding me… !

@mweinelt mweinelt merged commit eef4e9f into master Nov 6, 2023
@mweinelt mweinelt deleted the revert-265846-rsync branch November 6, 2023 16:39
Mic92 pushed a commit to Mic92/nixpkgs that referenced this pull request Nov 6, 2023
This reverts commit ad38853.

This change while correct causes a mass-rebuild and needs to be resubmitted for staging.
Mic92 pushed a commit that referenced this pull request Nov 7, 2023
This reverts commit ad38853.

This change while correct causes a mass-rebuild and needs to be resubmitted for staging.
@cafkafk cafkafk mentioned this pull request Nov 9, 2023
13 tasks
nyabinary pushed a commit to nyabinary/nixpkgs that referenced this pull request Nov 14, 2023
This reverts commit ad38853.

This change while correct causes a mass-rebuild and needs to be resubmitted for staging.
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.

4 participants