Git development
 help / color / mirror / Atom feed
From: "Francesco Pretto" <ceztkoml@gmail.com>
To: git@vger.kernel.org
Subject: Re: [PATCH] Implement selectable group ownership in git-init
Date: Sat, 3 Nov 2007 20:36:07 +0100	[thread overview]
Message-ID: <b13782500711031236k6b4faef9oe5780cb39afe25db@mail.gmail.com> (raw)
In-Reply-To: <472CC676.3000603@gmail.com>

2007/11/3, Francesco Pretto <ceztkoml@gmail.com>:
> Rationale ...

Just to point, I wrote this patch for usability purpose and because i
think git still need a strong imprinting about its correct usage
pattern (i've read around that people using it with shared
repositories are already having problems with file permissions,
wrongly thinking it's inflexible for their needs). If you stand with
my reasoning, please help me to integrate this patch :-), I have other
ideas following this. NB: i'm not a C developer (that was my first
patch in pure C), have mercy...

The function adjust_shared_perm is used in other places: is there
other git commands that maybe needs to create files/dirs of a specific
group (not being in a g+sx dir)? Hopefully not, but i don't know git
source much. These are the occurrences (with the exclusion of
builtin-init-db.c):

refs.c: adjust_shared_perm(log_file);
refs.c: if (adjust_shared_perm(git_HEAD)) {
..
builtin-pack-objects.c: return adjust_shared_perm(path);
...
builtin-rerere.c:           (mkdir(rr_cache, 0777) ||
adjust_shared_perm(rr_cache)))
...
lockfile.c:             if (adjust_shared_perm(lk->filename))
...
sha1_file.c:            else if (adjust_shared_perm(path)) {

  reply	other threads:[~2007-11-03 19:36 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 [this message]
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
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=b13782500711031236k6b4faef9oe5780cb39afe25db@mail.gmail.com \
    --to=ceztkoml@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.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox