git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: D Herring <dherring@tentpost.com>
To: git@vger.kernel.org
Subject: working directory umask
Date: Tue, 02 Feb 2010 01:30:32 -0500	[thread overview]
Message-ID: <hk8gq7$o76$1@ger.gmane.org> (raw)

Hi all,

So for one project at work, we have a (slow) server with a common 
build area.  Standard practice has been to extract a tarball, 
configure, make, make install into a common area.  I have started 
using git to replace the tarballs -- keep version info, make doesn't 
have to rebuild everything, auto-tag install sources, etc.

One problem:  Even though the working directory is g+swx and git was 
initialized with --shared=group or --shared=0660, the checked out 
source files still don't have group write permissions...

Is there an option that I've overlooked?  I can't seem to find 
anything that overrides umask in the working directory, only in the repo.

Thanks,
Daniel

             reply	other threads:[~2010-02-02  6:31 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-02  6:30 D Herring [this message]
2010-02-02  6:43 ` working directory umask Junio C Hamano

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='hk8gq7$o76$1@ger.gmane.org' \
    --to=dherring@tentpost.com \
    --cc=git@vger.kernel.org \
    /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).