On Wed, Oct 22, 2008 at 08:00:11PM +1100, Brett Ryan wrote: > Greetings, the reason I ask this question is because my pattern of > development is to create local source git repositories on my home > directory, then pull them to the central location. I found myself > getting the error `unable to create temporary sha1 filename > .git/objects/11: File exists' which after investigation found that > there were paths in `.git/objects/' owned by root which is who I use > to do the pull from my home directory using sudo. Aeh.. about which repo are you talking here? I guess it's not the one owned by root because otherwise this would be normal.. Hi Brett, I'm not sure where the problem comes form. But I feel your dev cycle is kind of wired. If you can login as root using ssh you can also do it the "normal" (?) way: # user dir git remote add root_repo ssh://root@localhost/path-to-root-repo git pull root_repo # then resolve conflicts if any git push root_repo # update the root repo This way you always have conflicts in your local repo and never on the root one which is preferable (IMHO).. git-fetch doesn't list a way to access another repo by "su(do)" which might be the best way here ? This could be convinient because you would'nt have to setup an extra group to access the same repo as root and user (?) You're right that git pull *should not* modify any files from the repo its pulling from.. But I don't know enough about git internals to say more about this. All I know is that git clone might have created some hardlinks.. But I'm not sure how this interfers with file permissions. I hope someone else can give a more accurate reply. Marc Weber -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
