git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Dirk Süsserott" <newsletter@dirk.my1.cc>
To: "Ka-rlis Repsons" <karlis.repsons@gmail.com>
Cc: git@vger.kernel.org
Subject: Re: use git-daemon by git://IP/path?
Date: Fri, 12 Jun 2009 15:54:08 +0200	[thread overview]
Message-ID: <4A325E00.6050504@dirk.my1.cc> (raw)
In-Reply-To: <200906121213.13365.Karlis.Repsons@gmail.com>

Am 12.06.2009 14:13 schrieb Ka-rlis Repsons:
> Hello git users and writers!
> 
> I am new to git, but, having read manuals and grasping the concepts of it, I 
> would like to first say thanks to all those, who created it!
> 
> Things would be fine, but I am having really bad ssh permission problems in 
> here: for example, if there is an empty, initialised git archive and it is 
> pulled to over ssh, the created files have permissions only u=rwX, no more. 
> Then subsequently git pulling doesn't work. Maybe you know how to solve it?

Probably your umask is doing this? When you locally create a file (e.g. 
"touch foo"), does it then only have "-rwx------" as well?

> Also, in general, how can it be set up, that >1 people have a write access to 
> the same repository? Only by using the same login? 

Have a look at the "--shared" option of "git init". That's supposed to 
create shared repositories, i.e. all users of the same group have write 
access. I'm not exactly sure how to make an existing repo "shared" after 
it's been created, but

$ git config core.sharedrepository 1

(which modifies .git/config) and a reasonable chown/chmod -R afterwards 
should work.

Hope this helps,
     Dirk

  reply	other threads:[~2009-06-12 13:55 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-12 12:13 use git-daemon by git://IP/path? Kārlis Repsons
2009-06-12 13:54 ` Dirk Süsserott [this message]
2009-06-12 14:16   ` Jeff King
2009-06-12 14:41     ` Dirk Süsserott
2009-06-12 14:24   ` git shared repository & permission problems Kārlis Repsons
2009-06-12 15:48 ` use git-daemon by git://IP/path? Pau Garcia i Quiles

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=4A325E00.6050504@dirk.my1.cc \
    --to=newsletter@dirk.my1.cc \
    --cc=git@vger.kernel.org \
    --cc=karlis.repsons@gmail.com \
    /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).