From: Heiko Voigt <hvoigt@hvoigt.net>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org, tv@eagain.net
Subject: Re: Re: [PATCH] Add USER environment variable to executed git commands when serving
Date: Wed, 3 Jun 2009 22:27:02 +0200 [thread overview]
Message-ID: <20090603202701.GA8739@macbook.lan> (raw)
In-Reply-To: <2e24e5b90906022324pe6769d5vfa5e3eec44daeaf3@mail.gmail.com>
On Wed, Jun 03, 2009 at 11:54:50AM +0530, Sitaram Chamarty wrote:
> On Wed, Jun 3, 2009 at 6:34 AM, Sitaram Chamarty <sitaramc@gmail.com> wrote:
>
> > I will test it out today at work and report back but it should work; I
> > don't see why it wouldn't, unless somewhere else there's a
> > sanitisation of env vars going on for security.
>
> works beautifully! Thanks again.
You are welcome. An interesting addition would be to propagate allowed
branchnames from gitosis.conf. That way you can implement write-
protected branches using an update hook.
Which enables better support for a maintainer based workflow for
centralized setups. Every developer would be allowed to push all branch
names he likes but the master branch is only writable by the maintainer.
A nice solution to steer this directly from gitosis.conf? I never got
around implementing it.
cheers Heiko
next prev parent reply other threads:[~2009-06-03 20:27 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-02 4:02 gitosis question: identifying/logging remote user Sitaram Chamarty
2009-06-02 6:31 ` Robin H. Johnson
2009-06-02 13:19 ` Sitaram Chamarty
2009-06-02 20:21 ` Robin H. Johnson
2009-06-03 0:54 ` Sitaram Chamarty
2009-06-02 13:56 ` [PATCH] Add USER environment variable to executed git commands when serving Heiko Voigt
2009-06-03 1:04 ` Sitaram Chamarty
2009-06-03 6:24 ` Sitaram Chamarty
2009-06-03 20:27 ` Heiko Voigt [this message]
2009-06-03 20:50 ` Robin H. Johnson
2009-06-03 21:02 ` Shawn O. Pearce
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=20090603202701.GA8739@macbook.lan \
--to=hvoigt@hvoigt.net \
--cc=git@vger.kernel.org \
--cc=sitaramc@gmail.com \
--cc=tv@eagain.net \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.