From: Junio C Hamano <gitster@pobox.com>
To: D Herring <dherring@tentpost.com>
Cc: git@vger.kernel.org
Subject: Re: working directory umask
Date: Mon, 01 Feb 2010 22:43:14 -0800 [thread overview]
Message-ID: <7v8wbccf3x.fsf@alter.siamese.dyndns.org> (raw)
In-Reply-To: <hk8gq7$o76$1@ger.gmane.org> (D. Herring's message of "Tue\, 02 Feb 2010 01\:30\:32 -0500")
D Herring <dherring@tentpost.com> writes:
> 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...
It is working as designed. "shared" setting is about a shared central
repository that is typically a bare repository, and currently it is
implemented as such.
You could argue that the behaviour for the work tree files is undefined
and make the code act differently, though.
In any case, it would be better to document this, and it might even make
sense to issue a warning message when we detect the repository is used
with a work tree (including the use of GIT_DIR and GIT_WORK_TREE
environment variables to temporarily turn a bare repository with a work
tree).
Thanks for a report.
prev parent reply other threads:[~2010-02-02 6:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-02 6:30 working directory umask D Herring
2010-02-02 6:43 ` Junio C Hamano [this message]
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=7v8wbccf3x.fsf@alter.siamese.dyndns.org \
--to=gitster@pobox.com \
--cc=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).