All of lore.kernel.org
 help / color / mirror / Atom feed
From: Neal Kreitzinger <nkreitzinger@gmail.com>
To: Levend Sayar <levendsayar@gmail.com>
Cc: git <git@vger.kernel.org>
Subject: Re: git repo corruption
Date: Tue, 04 Jan 2011 15:42:40 -0600	[thread overview]
Message-ID: <4D239450.2010509@gmail.com> (raw)
In-Reply-To: <AANLkTi=TSy1WQZARNQgGfPiV93hQ-xmCTip75JAixgDB@mail.gmail.com>

On 1/4/2011 3:10 AM, Levend Sayar wrote:
> Hi, all.
>
> We have a repo on a corporate server. The sysadmin changed access
> rights of files on our repo by accedant.
> Some directories have 2750 acces rights before, but he changed as
>
> chmod -R 2770 *
>
> Now when you make git status, every file that is tracked by git is said as
>
> changed but not updated
>
> So is there a way to get this back to normal ?
>
> TIA
>
> _lvnd_
> (^_^)

I assume the correct permissions for your tracked files should be 2750? 
  If so, then here's what I would do:

1.  First make a copy of your repo and test these steps on the copy:

e.g.  bare repo:  cp -rvp repo.git repocopy.git
non-bare-repo:  cp -rvp worktree worktreecopy

2. Then cd to the parent of the objects dir in you git repo:

e.g.  bare repo:  cd repocopy.git
non-bare repo:  cd worktreecopy/.git

3.  Then change the permissions of your objects dir:

chmod -R 2750 objects

4.  Validate the results.  Your permissions should match again.

5.  If it worked, then do it on the real repo.


v/r,
Neal

  parent reply	other threads:[~2011-01-04 21:43 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-01-04  9:10 git repo corruption Levend Sayar
2011-01-04 12:34 ` Drew Northup
2011-01-04 21:42 ` Neal Kreitzinger [this message]
2011-01-05 18:33 ` Neal Kreitzinger
2011-01-05 18:58   ` Levend Sayar
2011-01-05 19:49     ` Jakub Narebski

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=4D239450.2010509@gmail.com \
    --to=nkreitzinger@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=levendsayar@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.