Databases
StackOverflow2013
Postsdbo
POGit changes the permissions on a single file unexplainably
 

Note that there are some explanatory texts on larger screens.

plurals
  1. POGit changes the permissions on a single file unexplainably
    primarykey
    data
    text
    <p>I am the only person involved with this git project. Every time I edit files at my local Ubuntu repository, then push to Bitbucket and pull to my production repository, git changes the edited files to -rwxrwxr-x 775. Apache doesn't like this.</p> <p>Local system: git version 1.8.1.2 on Ubuntu Linux</p> <p>Production system: git version 1.7.12 on CentOS/Red Hat Linux</p> <p>When I fix permissions to 755, then do</p> <pre><code>git diff </code></pre> <p>or </p> <pre><code>git diff -p </code></pre> <p>It shows nothing.</p> <p>At my local repository, the permissions are 755 and the files are all owned by haws. At my production repository, all other permissions stay at 755, and all files including contact.php are owned by my username.</p> <p>At both the local and the production repository, I changed core.filemode as follows in an attempt to stop this behavior, </p> <pre><code>core.filemode = false </code></pre> <p>I've had mysteries like this in collaborative projects, so I'd really like to understand what's happening.</p> <ol> <li>What can I do to see git's reason for changing the permissions of this file?</li> <li>How can I get git to stop changing it?</li> </ol> <p>I have also tried to find the solution here: <a href="https://stackoverflow.com/questions/12733452/prevent-git-from-changing-permissions-on-pull">Prevent Git from changing permissions on pull</a> to no avail.</p> <p><strong>My Final Solution (thanks to VonC's guidance):</strong></p> <ol> <li><p>Thanks to VonC's good explanations, I was brave enough to figure out that every time I was logging into my server, my umask was going back to 0002. So I created a user startup script (.bashrc or in my case .bash_profile) at my Linux host that sets</p> <p>umask 0022</p></li> </ol> <p>or using symbolic notation (for a little added value)</p> <pre><code>umask u=a,g-w,o-w </code></pre> <p>or</p> <pre><code>umask u=a,go-w </code></pre> <p>(Allow all permissions for user, disallow write permissions for group and others)</p> <p>That solved my issue.</p> <ol start="2"> <li>I had previously set git config core.sharedRepository true, but that was not my issue, and I removed the setting once the issue was resolved. </li> </ol>
    singulars
    1. PO
      singulars
      1. PTAnswer
    1. This table or related slice is empty.
    1. PTQuestion
    1. USCommunity
    1. USTom Haws
    plurals
    1. PL
      singulars
      1. LTLinked
    2. PL
      singulars
      1. LTLinked
    3. PL
      singulars
      1. LTLinked
    1. PL
      singulars
      1. LTLinked
    1. This table or related slice is empty.
    1. PO
      singulars
      1. PTAnswer
    1. VO
      singulars
      1. POGit changes the permissions on a single file unexplainably
      1. USTom Haws
      1. VTBountyStart
    2. VO
      singulars
      1. POGit changes the permissions on a single file unexplainably
      1. This table or related slice is empty.
      1. VTUpMod
    3. VO
      singulars
      1. POGit changes the permissions on a single file unexplainably
      1. USVonC
      1. VTFavorite
    1. COSee the comment on October 16 2009 http://stackoverflow.com/questions/1580596/how-do-i-make-git-ignore-mode-changes-chmod Also it may have to do with the way you are adding the files to the working tree (git add . vs git commit -a)
      singulars
      1. POGit changes the permissions on a single file unexplainably
      1. USspuder
    2. COTurning core.filemode to false is probably not a bad workaround. And maybe it's not a bad standard work flow practice either. Still, I'd like to know why git is not "working as advertised". What am I overlooking?
      singulars
      1. POGit changes the permissions on a single file unexplainably
      1. USTom Haws
    3. COI suggest mentioning your operating system and git version for better and clearer answers. There are differences here with respect to windows, and non-windows systems.
      singulars
      1. POGit changes the permissions on a single file unexplainably
      1. USArafangion
 

Querying!

 
Guidance
A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload