From: Aaron Schrab <aaron@schrab.com>
To: Christopher Dale <chrelad@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: Adding hooks.directory config option; wiring into run_hook
Date: Fri, 16 Dec 2011 20:58:21 -0500 [thread overview]
Message-ID: <20111217015820.GC30928@pug.qqx.org> (raw)
In-Reply-To: <CADQnX_e76LzuRUDOKFOsRHU=e8Cw+qh5x1BdW5HMEdMmP5PaHg@mail.gmail.com>
At 12:00 -0600 16 Dec 2011, Christopher Dale <chrelad@gmail.com> wrote:
>Since the hooks directory is within a directory that by it's very
>nature requires write permissions,
Are you sure about this? I'd think that this would mainly be used for
bare repositories. For a test I created a bare repository, removed
write permission, changed the owner to root, then pushed into it from
another repository. So it seems that, at least for basic usage, a bare
repository can be modified even if with write permission removed since
no entries are being created or removed at the top level.
For this to be a workaround, new repositories would need to be created
by an admin. The requirement that the containing directory not be
writeable wouldn't necessarily be an issue; at least on Linux I'm able
to create files/directories as root even in a non-writeable directory.
prev parent reply other threads:[~2011-12-17 2:06 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-16 18:00 [PATCH] Adding hooks.directory config option; wiring into run_hook Christopher Dale
2011-12-16 18:06 ` Junio C Hamano
2011-12-16 18:28 ` Christopher Dale
2011-12-16 19:23 ` Junio C Hamano
2011-12-17 3:03 ` Aaron Schrab
2011-12-17 1:58 ` Aaron Schrab [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=20111217015820.GC30928@pug.qqx.org \
--to=aaron@schrab.com \
--cc=chrelad@gmail.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).