use git-daemon by git://IP/path?

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?

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? 

Kind regards,
Kārlis

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

On Fri, Jun 12, 2009 at 03:54:08PM +0200, Dirk Süsserott wrote:

quoted

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  

I have also had good experiences with POSIX ACLs for sharing
repositories:

  setfacl -R -m d:u:$user:rwX -m u:$user:rwX /path/to/repo

which gets rid of dealing with group management.  Of course your
filesystem has to support them. :)

-Peff

On Friday 12 June 2009 13:54:08 you wrote:

Am 12.06.2009 14:13 schrieb Ka-rlis Repsons:

quoted

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?

quoted

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.

Am 12.06.2009 16:16 schrieb Jeff King:

On Fri, Jun 12, 2009 at 03:54:08PM +0200, Dirk Süsserott wrote:

quoted

quoted

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  

I have also had good experiences with POSIX ACLs for sharing
repositories:

  setfacl -R -m d:u:$user:rwX -m u:$user:rwX /path/to/repo

which gets rid of dealing with group management.  Of course your
filesystem has to support them. :)

That's the best way, of course. We use it at work to have 'release'
repositories where only a dedicated maintainer and his deputy can
push to. Our developers push to their 'public' repos and the maintainer
then pulls their changes and pushes them to 'release' -- just like Junio 
does here :-)

     Dirk

Hello,

If you are not concerned about security, just make your repository public:

http://www.elpauer.org/?p=337

On Fri, Jun 12, 2009 at 2:13 PM, Kārlis Repsons[off-list ref] wrote:

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?

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?

Kind regards,
Kārlis

-- 
Pau Garcia i Quiles
http://www.elpauer.org
(Due to my workload, I may need 10 days to answer)