git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Eugene Sajine <euguess@gmail.com>
To: sconeman <schoen@bu.edu>
Cc: git@vger.kernel.org
Subject: Re: get git not to care about permissions
Date: Thu, 12 Nov 2009 10:28:57 -0500	[thread overview]
Message-ID: <76c5b8580911120728j2f9995basb554b0a493a364bf@mail.gmail.com> (raw)
In-Reply-To: <76c5b8580911111334p76232995qbd6bf6b06d250854@mail.gmail.com>

>>
>> On Nov 9, 2009 11:06 AM, "sconeman" <schoen@bu.edu> wrote:
>>
>>
>> Hello,
>>
>> I'm trying to set up git on a NetApp drive at my school, BU.  The NetApp
>> shares are configured with Windows permissions, and I forget the specifics
>> (which I can figure out if needed) about why this is the case, but basically
>> the deal is that if true UNIX permissions were to be used, Windows wouldn't
>> be able to read the drive.  As such, and because we use the Kerberos
>> ticketing system, the permissions for the drive are set up such that the
>> owners (myself and my team members) have full permissions, but nobody else
>> does.  Git doesn't like this and won't even create a bare repository.  Is
>> there any way I can get git to ignore permissions and just do what it needs
>> to do?
>>
>> Thanks in advance for the help!
>>
>> -Matt
> --
On Wed, Nov 11, 2009 at 4:34 PM, Eugene Sajine <euguess@gmail.com> wrote:
> Hi,
>
> I had almost similar issue - bare repos in my case should be set up under
> user which only few guys are having password from. So what I did is just a
> small program which creates the bare repo locally and makes secure copy to
> this user home. All authentication is hidden from the end user. Then users
> can access their repos via git protocol. Ialso fillthe repo with some
> additional info for cgit.
>
> Eugene

BTW I'm using "git clone --bare" in this process, so if you have a
repo with working copy you can create a bare one separately, put it on
the server and then connect to it via "git remote add"

Eugene

  parent reply	other threads:[~2009-11-12 15:29 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 16:06 get git not to care about permissions sconeman
2009-11-12  5:44 ` Jay Soffian
2009-11-12 15:44   ` Matt Schoen
2009-11-12 16:10     ` Thomas Rast
2009-11-12 21:44       ` Matt Schoen
2009-11-15 12:31         ` Thomas Rast
     [not found] ` <76c5b8580911111327k43daece9s2e71d0a2b8adcebd@mail.gmail.com>
     [not found]   ` <76c5b8580911111334p76232995qbd6bf6b06d250854@mail.gmail.com>
2009-11-12 15:28     ` Eugene Sajine [this message]
2009-11-12 15:47       ` Matt Schoen

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=76c5b8580911120728j2f9995basb554b0a493a364bf@mail.gmail.com \
    --to=euguess@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=schoen@bu.edu \
    /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).