From: Heiko Voigt <hvoigt@hvoigt.net>
To: Sitaram Chamarty <sitaramc@gmail.com>
Cc: git@vger.kernel.org, tv@eagain.net
Subject: [PATCH] Add USER environment variable to executed git commands when serving
Date: Tue, 2 Jun 2009 15:56:59 +0200 [thread overview]
Message-ID: <20090602135659.GA4320@macbook.lan> (raw)
In-Reply-To: <2e24e5b90906012102y4e1e6281p437e4d88da517c08@mail.gmail.com>
This is useful if you want to implement access rights by branchname.
The update hook can check this variable and react accordingly.
Signed-off-by: Heiko Voigt <hvoigt@hvoigt.net>
---
On Tue, Jun 02, 2009 at 09:32:40AM +0530, Sitaram Chamarty wrote:
> I'd like it to set an additional env var which will contain "username"
> so that hooks etc can get that info and use it as they they see fit.
Here is a trivial patch. This is totally untested as I wanted to
implement something similar but never had the time to work more on it.
cheers Heiko
gitosis/serve.py | 1 +
1 files changed, 1 insertions(+), 0 deletions(-)
diff --git a/gitosis/serve.py b/gitosis/serve.py
index 867249e..0e2c4af 100644
--- a/gitosis/serve.py
+++ b/gitosis/serve.py
@@ -201,6 +201,7 @@ class Main(app.App):
sys.exit(1)
main_log.debug('Serving %s', newcmd)
+ os.putenv('USER', user)
os.execvp('git', ['git', 'shell', '-c', newcmd])
main_log.error('Cannot execute git-shell.')
sys.exit(1)
--
1.6.2.1.424.g0b27.dirty
next prev parent reply other threads:[~2009-06-02 13:57 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 ` Heiko Voigt [this message]
2009-06-03 1:04 ` [PATCH] Add USER environment variable to executed git commands when serving Sitaram Chamarty
2009-06-03 6:24 ` Sitaram Chamarty
2009-06-03 20:27 ` Heiko Voigt
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090602135659.GA4320@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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).