ListingEmpty contains wrong @file

Here i am attaching a patch to correct it.
This is my first attempt to commit something. Please correct me if did any mistake.

Thanks -- it looks like you figured out patching correctly! I'll get this committed when I can.

Thank you..........

Looking for easy pickings, so... :)

Committed to 8.x. Thanks! Will push once testbot is caught up.

diff --git a/core/modules/node/lib/Drupal/node/Plugin/views/area/ListingEmpty.php b/core/modules/node/lib/Drupal/node/Plugin/views/area/ListingEmpty.php
old mode 100644
new mode 100755

:(

I dont know what that means...
but can we just make a patch to reverse that?

diff --git a/core/modules/node/lib/Drupal/node/Plugin/views/area/ListingEmpty.php b/core/modules/node/lib/Drupal/node/Plugin/views/area/ListingEmpty.php
old mode 100755
new mode 100644

--

If someone knows a link to more info about that... I'll try google.
http://stackoverflow.com/questions/1257592/removing-files-saying-old-mod...
oh, maybe something about permissions! 755, 644

so maybe the way to make a new patch here, is to change the permissions back on that file, and then do a git diff in the usual way.

These are not the only files with wrong permissions there are alot of files with wrong permissions we should start a followup.
@YesCT Securing file permissions and ownership

whoa. I think here we should just fix this one caused by this commit.

Or, just take care of it (them all) in a follow-up.

Actually, I would suggest we just do this one here. AND do a follow-up for the rest of them.

Patch as per #10

rtbc if green.

yes we should fix just just the one introduced here..thanks for the patch and sorry for not being descriptive

As discussed with YesCT, just reposting the patch to correct file permission on core/modules/node/lib/Drupal/node/Plugin/views/area/ListingEmpty.php

Committed this patch.

Can someone file an issue to fix the other permissions problems?

Created #1948148: Update file permissions

Thanks @calmher

Sometimes we want to retest a patch that is already posted, and we use the re-test link on the comment that has the patch. I think that helps eliminate confusion of posting same patches. :)