From: "Jan Krüger" <jk@jk.gs>
To: "Ferry Huberts (Pelagic)" <ferry.huberts@pelagic.nl>
Cc: Git Mailing List <git@vger.kernel.org>
Subject: Re: git init permissions?
Date: Tue, 14 Apr 2009 20:40:24 +0200 [thread overview]
Message-ID: <20090414204024.5371fcac@perceptron> (raw)
In-Reply-To: <49E4D16E.9050500@pelagic.nl>
Hi,
On Tue, 14 Apr 2009 20:09:50 +0200, "Ferry Huberts (Pelagic)"
<ferry.huberts@pelagic.nl> wrote:
> Is there some kind of reason that the branches directory is
> not created with +s permissions?
Probably because it isn't really used anymore. It's more like a
historical artifact. Branch refs actually live in refs/heads/ and the
like (or in the packed-refs file).
-Jan
next prev parent reply other threads:[~2009-04-14 18:42 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 [this message]
2009-04-14 18:47 ` Johan Herland
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=20090414204024.5371fcac@perceptron \
--to=jk@jk.gs \
--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).