From: Andrew Ruder <andy@aeruder.net>
To: Stefan Beller <stefanbeller@googlemail.com>
Cc: Justin Collum <jcollum@gmail.com>, git@vger.kernel.org
Subject: Re: git status resets permissions on index file -- Ubuntu 12.04 64b
Date: Thu, 8 Aug 2013 17:18:07 -0500 [thread overview]
Message-ID: <20130808221807.GA8518@gmail.com> (raw)
In-Reply-To: <52040F27.4050908@googlemail.com>
On Thu, Aug 08, 2013 at 11:35:35PM +0200, Stefan Beller wrote:
> On 08/08/2013 10:27 PM, Justin Collum wrote:
> > [...]
> > -rwxrwxrwx 1 dev dev 17K Aug 8 13:12 index
> > [...]
> > -rw-rw-r-- 1 dev dev 17K Aug 8 13:16 index # <---------------
>
> The permissions are set to reading for all and writing for you(r user)
> and your group. This should be no problem with standard git commands.
> Before you had the index file executable, why would you need that?
I'm about 90% sure the issue he's having is that the write bit for
other/world goes away and he is neither the user dev or the group dev
and the reason for all the executable bits is that he is regularly
running
chmod -R 777 .
Justin, if this is true, I will tell you that git respects your umask
but I just can't bring myself to really suggest someone type umask 000
ever. :(
- Andy
next prev parent reply other threads:[~2013-08-08 22:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-08 20:27 git status resets permissions on index file -- Ubuntu 12.04 64b Justin Collum
2013-08-08 21:35 ` Stefan Beller
2013-08-08 22:18 ` Andrew Ruder [this message]
2013-08-08 22:33 ` Justin Collum
2013-08-08 23:00 ` Andrew Ruder
2013-08-08 22:37 ` Kyle J. McKay
2013-08-08 23:58 ` Justin Collum
2013-08-09 12:40 ` Andreas Schwab
2013-08-09 12:58 ` Matthieu Moy
2013-08-09 17:00 ` Justin Collum
2013-08-09 19:29 ` Justin Collum
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20130808221807.GA8518@gmail.com \
--to=andy@aeruder.net \
--cc=git@vger.kernel.org \
--cc=jcollum@gmail.com \
--cc=stefanbeller@googlemail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).