From: Johan Herland <johan@herland.net>
To: git@vger.kernel.org
Cc: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
Subject: Re: git init permissions?
Date: Tue, 14 Apr 2009 20:47:21 +0200 [thread overview]
Message-ID: <200904142047.21810.johan@herland.net> (raw)
In-Reply-To: <49E4D16E.9050500@pelagic.nl>
On Tuesday 14 April 2009, Ferry Huberts (Pelagic) wrote:
> I'm looking at the git init --shared=group result and see:
>
> drwxrwsr-x 7 ferry ferry 111 2009-04-14 19:51 .
> drwxrwxr-x 3 ferry ferry 17 2009-04-14 19:51 ..
> drwxrwxr-x 2 ferry ferry 6 2009-04-14 19:51 branches
> -rw-rw-r-- 1 ferry ferry 127 2009-04-14 19:51 config
> -rw-rw-r-- 1 ferry ferry 58 2009-04-14 19:51 description
> -rw-rw-r-- 1 ferry ferry 23 2009-04-14 19:51 HEAD
> drwxrwxr-x 2 ferry ferry 4.0K 2009-04-14 19:51 hooks
> drwxrwxr-x 2 ferry ferry 20 2009-04-14 19:51 info
> drwxrwsr-x 4 ferry ferry 28 2009-04-14 19:51 objects
> drwxrwsr-x 4 ferry ferry 29 2009-04-14 19:51 refs
>
> Is there some kind of reason that the branches directory is
> not created with +s permissions?
>
> I can understand it for the hooks and info directories since
> you can not push into those. You _can_ however push into
> branches and I would expect it to have +s too, like objects
> and refs.
>
> Bug or my misunderstanding?
>
> git version 1.6.0.6
This was caused by the template files not getting adjusted permissions set
correctly when copied into a new repository (by git init).
This has been fixed (along with other --shared issues) in v1.6.2.3. Please
upgrade, if possible.
Have fun! :)
...Johan
--
Johan Herland, <johan@herland.net>
www.herland.net
next prev parent reply other threads:[~2009-04-14 18:49 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-14 18:09 git init permissions? Ferry Huberts (Pelagic)
2009-04-14 18:40 ` Jan Krüger
2009-04-14 18:47 ` Johan Herland [this message]
2009-04-14 19:35 ` Ferry Huberts (Pelagic)
2009-04-15 1:02 ` Todd Zullinger
2009-04-23 20:50 ` Ferry Huberts (Pelagic)
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=200904142047.21810.johan@herland.net \
--to=johan@herland.net \
--cc=ferry.huberts@pelagic.nl \
--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).