From: "Kārlis Repsons" <karlis.repsons@gmail.com>
To: git@vger.kernel.org
Subject: Re: git shared repository & permission problems
Date: Fri, 12 Jun 2009 14:24:24 +0000 [thread overview]
Message-ID: <200906121424.28577.Karlis.Repsons@gmail.com> (raw)
In-Reply-To: <4A325E00.6050504@dirk.my1.cc>
[-- Attachment #1: Type: text/plain, Size: 1236 bytes --]
On Friday 12 June 2009 13:54:08 you wrote:
> Am 12.06.2009 14:13 schrieb Ka-rlis Repsons:
> > 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?
No, at client its allright with umask (well, in bash, not konqueror).
Where from is sftp-server receiving its file permission bits for the new
files? Maybe some way to change it?
> > 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,
Someone else knows? That would be useful...
> Hope this helps,
> Dirk
Thanks!
k.
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-06-12 14:24 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
2009-06-12 14:16 ` Jeff King
2009-06-12 14:41 ` Dirk Süsserott
2009-06-12 14:24 ` Kārlis Repsons [this message]
2009-06-12 15:48 ` 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
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=200906121424.28577.Karlis.Repsons@gmail.com \
--to=karlis.repsons@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.
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).