Git development
 help / color / mirror / Atom feed
From: Francesco Pretto <ceztkoml@gmail.com>
To: Wincent Colaiuta <win@wincent.com>
Cc: Junio C Hamano <gitster@pobox.com>, git@vger.kernel.org
Subject: Re: [PATCH] Implement selectable group ownership in git-init
Date: Mon, 05 Nov 2007 16:09:06 +0100	[thread overview]
Message-ID: <472F3212.4090800@gmail.com> (raw)
In-Reply-To: <8EF5148D-C1F0-4329-A221-82D0B7E9932C@wincent.com>

Wincent Colaiuta ha scritto:
> 
> using the administration tools designed for managing access, just like
> every other SCM (and every server, and every piece of software which can
> be accessed by many on a multi-user system).
> 

I don't agree in general: in SCMs and other multi-user softwares, the access
control configuration can be safely postponed just because it's in their
standard usage pattern that the access should be conditioned by a daemon
to be configured later. It's not the case of git, just because git is very
tied to *nix permissions.
But as it is now, it could seems that it's good to put committers in the (for
example) git group, just because you have a git administrative account
git:git . This is caused, imo, by the fact that the flow of creating a shared
repository for a specific work/project group with git-init run by an
administrative user (as it should be) is something like this:

	- Do it wrong;
	- Fix it immediately.

I don't like the "Do it wrong" part. I'm trying to produce a sane and
transparent patch to implement the selectable group just in case of repository
first initialization. Why do I care so much of first time users? Dunno, but
I think it's important.

  reply	other threads:[~2007-11-05 15:09 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-11-03 19:05 [PATCH] Implement selectable group ownership in git-init Francesco Pretto
2007-11-03 19:36 ` Francesco Pretto
2007-11-03 22:27 ` Junio C Hamano
2007-11-03 22:31   ` Junio C Hamano
2007-11-05 13:49   ` Wincent Colaiuta
2007-11-05 15:09     ` Francesco Pretto [this message]
2007-11-05 15:26       ` Wincent Colaiuta
2007-11-05 22:27     ` Francesco Pretto
2007-11-06 10:31       ` Wincent Colaiuta

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=472F3212.4090800@gmail.com \
    --to=ceztkoml@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.com \
    --cc=win@wincent.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