From: "Martin Langhoff" <martin.langhoff@gmail.com>
To: "Linus Torvalds" <torvalds@osdl.org>
Cc: "Bill Lear" <rael@zopyra.com>,
"Jakub Narebski" <jnareb@gmail.com>,
"Git Mailing List" <git@vger.kernel.org>
Subject: Re: git-push through git protocol
Date: Mon, 22 Jan 2007 15:26:18 +1300 [thread overview]
Message-ID: <46a038f90701211826v54340352lf4376db41ad5be37@mail.gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.64.0701211749140.14248@woody.osdl.org>
On 1/22/07, Linus Torvalds <torvalds@osdl.org> wrote:
> Umm. Your git daemon is probably running as "nobody", and simply doesn't
> have write permissions to the archive, does it?
>
> > % cat /etc/xinet.d/git-daemon
> > service git
> > {
> > user = nobody
>
> iow, I think you simply need to make sure that git-daemon will have write
> permission to the thing. Either by making the whole repository writable by
> nobody, or by running git-daemon as the proper user.
Whereby I personaly run back quickly to cover under my git-over-ssh
safety blanket.
:-)
martin
next prev parent reply other threads:[~2007-01-22 2:26 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-01-21 14:10 git-push through git protocol Bill Lear
2007-01-21 15:27 ` Jakub Narebski
2007-01-21 19:04 ` Linus Torvalds
2007-01-21 20:09 ` Bill Lear
2007-01-21 21:16 ` Johannes Schindelin
2007-01-21 21:22 ` Bill Lear
2007-01-21 22:00 ` Linus Torvalds
2007-01-22 0:17 ` Linus Torvalds
2007-01-22 0:50 ` Junio C Hamano
2007-01-22 1:10 ` [PATCH] Make sure git_connect() always give two file descriptors Junio C Hamano
2007-01-22 1:47 ` Linus Torvalds
2007-01-22 1:31 ` git-push through git protocol Bill Lear
2007-01-22 1:41 ` Bill Lear
2007-01-22 1:52 ` Linus Torvalds
2007-01-22 2:26 ` Martin Langhoff [this message]
2007-01-22 3:01 ` Linus Torvalds
2007-01-22 13:58 ` Bill Lear
2007-01-22 14:41 ` Bill Lear
2007-01-21 23:49 ` Martin Langhoff
2007-01-22 0:03 ` Bill Lear
2007-01-22 0:24 ` Martin Langhoff
2007-01-22 0:48 ` Jakub Narebski
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=46a038f90701211826v54340352lf4376db41ad5be37@mail.gmail.com \
--to=martin.langhoff@gmail.com \
--cc=git@vger.kernel.org \
--cc=jnareb@gmail.com \
--cc=rael@zopyra.com \
--cc=torvalds@osdl.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).