-
Notifications
You must be signed in to change notification settings - Fork 6.1k
8333477: Delete extra empty spaces in Makefiles #19537
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
Conversation
👋 Welcome back syan! A progress list of the required criteria for merging this PR into |
@sendaoYan This change now passes all automated pre-integration checks. ℹ️ This project also has non-automated pre-integration requirements. Please see the file CONTRIBUTING.md for details. After integration, the commit message for the final commit will be:
You can use pull request commands such as /summary, /contributor and /issue to adjust it as needed. At the time when this comment was updated there had been 76 new commits pushed to the
As there are no conflicts, your changes will automatically be rebased on top of these commits when integrating. If you prefer to avoid this automatic rebasing, please check the documentation for the /integrate command for further details. As you do not have Committer status in this project an existing Committer must agree to sponsor your change. Possible candidates are the reviewers of this PR (@erikj79, @chhagedorn, @TheShermanTanker) but any other Committer may sponsor as well. ➡️ To flag this PR as ready for integration with the above commit message, type |
@sendaoYan The following labels will be automatically applied to this pull request:
When this pull request is ready to be reviewed, an "RFR" email will be sent to the corresponding mailing lists. If you would like to change these labels, use the /label pull request command. |
Webrevs
|
/label build |
Thanks. |
@erikj79 |
Thanks for the review. |
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.
Looks good! Somehow the integrate command did not work.
Thanks all for the review. |
@sendaoYan |
@sendaoYan |
…ty/benchmark/bench/Makefile
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.
Thank you for the fix.
Thanks all for the review. |
@sendaoYan |
@@ -47,4 +47,3 @@ all: .classes | |||
|
|||
clean: | |||
rm -f *.class .classes | |||
|
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.
Hmm, shouldn't this newline at EOF be kept? Asking @ all the people who've reviewed this so far, no need to change it just yet
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.
No, it's an extra newline. A file should end with a newline but one is enough.
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.
As confusing as they are, unfortunately GitHub UI does not render extra trailing newlines. This is the only one I could find with grepWin.
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.
I find the extra trailing newlines through below shell command:
for i in `find . -iname "Makefile*" | sed "/\.\/build/d"` ; do tail -n 2 $i | grep -c "^$" | grep -q "^1$" ; if [[ 0 -eq $? ]] ; then echo $i ; fi ; done
There are only two files has been found:
./test/jdk/java/rmi/reliability/benchmark/bench/rmi/Makefile
./test/jdk/java/rmi/reliability/benchmark/bench/Makefile
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.
Ah, I had not realized that there was more than 1 newline. GitHub's UI confused me here, so we're good to go
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.
GitHub's UI assumes the final line has an line break. If it is missing, it displays a red 🚫 at the end of the last line. If there is an empty line showing up in the UI, then it is an additional empty line.
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.
In this case, GitHub is actually not showing up extra empty lines, that they appear the same as the single line break in the end of the file.
/sponsor |
Going to push as commit d130d2f.
Your commit was automatically rebased without conflicts. |
@TheShermanTanker @sendaoYan Pushed as commit d130d2f. 💡 You may see a message that your pull request was closed with unmerged commits. This can be safely ignored. |
Thanks all for the review and sponsor. |
Hi all,
This PR several extra empty spaces and extra empty lines in several Makefiles. It's trivial fix, no risk.
Thanks.
Progress
Issue
Reviewers
Reviewing
Using
git
Checkout this PR locally:
$ git fetch https://git.openjdk.org/jdk.git pull/19537/head:pull/19537
$ git checkout pull/19537
Update a local copy of the PR:
$ git checkout pull/19537
$ git pull https://git.openjdk.org/jdk.git pull/19537/head
Using Skara CLI tools
Checkout this PR locally:
$ git pr checkout 19537
View PR using the GUI difftool:
$ git pr show -t 19537
Using diff file
Download this PR as a diff file:
https://git.openjdk.org/jdk/pull/19537.diff
Webrev
Link to Webrev Comment