-
-
Notifications
You must be signed in to change notification settings - Fork 156
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
Add space to not-owned notices #196
Conversation
Good catch |
Huh, I just chowned this dir and file (to root) and now I have failing tests. Need to look further into this, but that's not supposed to happen, right? |
You have to make sure the files have the correct permissions too. I had to chmod and chown to get them to work locally. They work on travis so I'm not too concerned. |
They are working on my machine also. |
Yeah, my git sets not-owned.txt up with Interestingly though, git doesn't pick up a change if I chmod this file to But here it doesn't work. I played around a little, and it seems git only cares about the That it does work on Travis (and I presume Linux generally) but not on Mac makes me think the (default?) behaviour of Git is distinct in this regard. I have to call it day now but would suggest having the test check if the file has |
@phated I just quickly followed this up and added a notice about chmod to the not-owned test. It's more pedantry, I guess, sorry about that. I trust you'll let me know if it gets to be annoying... |
PS I may be missing something obvious, but why does the directory have to be chowned as well? The chown to root requires sudo anyway, so access to the directory should not be a problem. |
It probably doesn't need to be. I just did it to be safe. |
All right, I see. I didn't want to presume and make a PR of the chmod notice, but it's there if you want it. |
Feel free to send a PR. Easier for me to merge. |
Pedantic, I know, but it looked off :-)