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

Trim trailing whitespace from all source files throughout project #2892

Closed
wants to merge 1 commit into from

Conversation

jdufresne
Copy link
Contributor

Many editors trim whitespace by default. When newcomers are submitting patches, it is often undesirable to see inadvertent whitespace changes in the diff as it is distracting and unrelated. To make contributing easier, clean up all whitespace in one go across the project. Will allow for cleaner diffs in the future. Contributors will not need to worry about automatic yet inadvertent whitespace changes.

Many editors trim whitespace by default. When newcomers are submitting
patches, it is often undesirable to see inadvertent whitespace changes
in the diff as it is distracting and unrelated. To make contributing
easier, clean up all whitespace in one go across the project. Will allow
for cleaner diffs in the future. Contributors will not need to worry
about automatic yet inadvertent whitespace changes.
@radarhere
Copy link
Member

I will note that this PR wouldn't solve the problem you're describing once-and-for-all - I mean, it would go a long way towards it, but trailing whitespace is not just legacy code. Trailing whitespaces are commonly added in with new commits.

@wiredfool
Copy link
Member

So, while this may be useful to reduce noise in commits, I'm not going to merge it due to rebasing issues.

I'm trying to clear out the old backlog of PRs that are stacked up due to missing tests or needing one last tweak. If I merge this, it's likely to trigger rebase issues on those PRs, and that adds one more hurdle to getting those PRs in.

@wiredfool wiredfool closed this Dec 20, 2017
@jdufresne
Copy link
Contributor Author

If you finish the backlog and would like me to rebase or redo this work. Please let me know. I'm happy to. The change is done automatically by a simple command.

@jdufresne
Copy link
Contributor Author

I'm not going to merge it due to rebasing issues.

Given the recent code reorganziation, should this be reconsidered? I expect the code reorganization will already require a large amount of rebasing.

@wiredfool
Copy link
Member

Sure, I'll push this in

@hugovk hugovk mentioned this pull request Feb 27, 2018
@jdufresne jdufresne deleted the ws branch March 17, 2019 16:58
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.

None yet

3 participants