git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sitaram Chamarty <sitaramc@gmail.com>
To: Git Mailing List <git@vger.kernel.org>
Subject: running "git init --shared" on an existing repo
Date: Mon, 22 Mar 2010 12:00:01 +0530	[thread overview]
Message-ID: <2e24e5b91003212330r2f3fd118y18386ef61c28ee89@mail.gmail.com> (raw)

Hi all,

If you forget to use "--shared" on your (bare) repo, and now need to
adjist it after the fact to make perms work ok, you ought to be able
to just run "git init --bare --shared" and things should be fine.

And it seems there was a beginning made.  builtin/init-db.c at line 220 says:

            /*
             * We would have created the above under user's umask -- under
             * shared-repository settings, we would need to fix them up.
             */
            if (shared_repository) {
                    adjust_shared_perm(get_git_dir());
                    adjust_shared_perm(git_path("refs"));
                    adjust_shared_perm(git_path("refs/heads"));
                    adjust_shared_perm(git_path("refs/tags"));
            }

Ideally, we should do the same to:

hooks
info
objects
objects/??
objects/info
objects/pack

also.  The othes are easy, but does git internals have a defined way
of doing that objects/?? part or should it just be the long way (it's
been ages since I did any C but I'd be willing to try...)

--
Sitaram

             reply	other threads:[~2010-03-22  6:30 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-22  6:30 Sitaram Chamarty [this message]
2010-03-22  7:06 ` running "git init --shared" on an existing repo Junio C Hamano
     [not found]   ` <2e24e5b91003220244v2d21bf3ay5b18d1ef40781be2@mail.gmail.com>
2010-03-22  9:45     ` Fwd: " Sitaram Chamarty

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=2e24e5b91003212330r2f3fd118y18386ef61c28ee89@mail.gmail.com \
    --to=sitaramc@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;
as well as URLs for NNTP newsgroup(s).