From: "Dilip M" <dilipm79@gmail.com>
To: "Matthieu Moy" <Matthieu.Moy@imag.fr>
Cc: "Brian Foster" <brian.foster@innova-card.com>,
"Reece Dunn" <msclrhd@googlemail.com>,
"git list" <git@vger.kernel.org>
Subject: Re: gitk doesn't work w/o sudo.
Date: Tue, 20 Jan 2009 23:05:44 +0530 [thread overview]
Message-ID: <c94f8e120901200935t75dba11fw3ce14b4ba965c878@mail.gmail.com> (raw)
In-Reply-To: <vpq4oztgaz8.fsf@bauges.imag.fr>
On Tue, Jan 20, 2009 at 10:40 PM, Matthieu Moy <Matthieu.Moy@imag.fr> wrote:
> "Dilip M" <dilipm79@gmail.com> writes:
>
>>> repeating Reece's question, what is the permissions/owner
>>> _of_the_directory_which_contains_ the '.git/' directory?
>>> I can reproduce this behaviour (git 1.6.0.4) simply by
>>> denying myself search (née execute) permission on that
>>> directory, for entirely obvious reasons.
>>
>> It's the same issue....
>
> You didn't answer the question.
Sorry..I read it for .git directory...
.git's parent directory is owned by user who us issuing gitk command
and permisssion bit of 755 is set.
dm-laptop:~/repos/atria> ls -ld .
drwxr-xr-x 6 dm dm 4096 2009-01-18 23:28 .
dm-laptop:~/repos/atria> ls -ld .git/
drwxr-xr-x 8 dm dm 4096 2009-01-20 22:22 .git/
>> Any ENV variable I can set to debug this...?
>
> GIT_TRACE can help.
I tried with that but it didn't help for gitk. But sure, it helps with
git command(s).
-- DM
next prev parent reply other threads:[~2009-01-20 17:37 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-19 10:16 gitk doesn't work w/o sudo Dilip M
2009-01-19 11:59 ` Reece Dunn
2009-01-19 14:37 ` Dilip M
2009-01-20 8:12 ` Brian Foster
2009-01-20 16:51 ` Dilip M
2009-01-20 17:10 ` Matthieu Moy
2009-01-20 17:35 ` Dilip M [this message]
2009-01-20 18:00 ` Reece Dunn
2009-01-20 17:16 ` Johannes Schindelin
2009-01-20 18:20 ` Dilip M
2009-01-20 21:10 ` Johannes Schindelin
2009-01-19 14:48 ` Jing Xue
2009-01-19 15:35 ` Dilip M
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=c94f8e120901200935t75dba11fw3ce14b4ba965c878@mail.gmail.com \
--to=dilipm79@gmail.com \
--cc=Matthieu.Moy@imag.fr \
--cc=brian.foster@innova-card.com \
--cc=git@vger.kernel.org \
--cc=msclrhd@googlemail.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 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).