From: William Pursell <bill.pursell@gmail.com>
To: git@vger.kernel.org
Subject: permissions
Date: Fri, 04 Jun 2010 23:33:50 -1000 [thread overview]
Message-ID: <4C0A19FE.1020802@wpursell.net> (raw)
If .git is not readable, but ../.git is, .git works with
the database in ../.git. Is that the desired behavior?
It would seem more appropriate that git fail with a
"permission denied" error. In particular, if .git
is not readable and there is no database between
$PWD and $GIT_CEILING_DIRECTORIES, the current error is:
fatal: Not a git repository (or any of the parent directories): .git
Wouldn't it be better to have the error message be something like:
.git: permission denied
After all, it is a git repository, so "Not a git repository"
is not accurate.
--
William Pursell
next reply other threads:[~2010-06-05 9:34 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 9:33 William Pursell [this message]
2010-06-05 9:50 ` permissions Andreas Schwab
2010-06-05 18:23 ` permissions William Pursell
2010-06-06 6:45 ` permissions Alex Riesen
2010-06-06 9:36 ` permissions William Pursell
2010-06-06 12:45 ` permissions Alex Riesen
2010-06-06 19:54 ` permissions Junio C Hamano
2010-06-08 10:25 ` permissions William Pursell
2010-06-08 14:52 ` permissions Alex Riesen
2010-06-08 21:05 ` permissions Junio C Hamano
2010-06-08 22:27 ` permissions William Pursell
2010-06-09 7:20 ` permissions Alex Riesen
2010-06-09 10:29 ` permissions William Pursell
2010-06-09 12:06 ` permissions Thomas Rast
2010-06-09 13:00 ` permissions Alex Riesen
2010-06-09 12:56 ` permissions Alex Riesen
2010-06-09 10:39 ` permissions Steven Michalske
-- strict thread matches above, loose matches on Subject: below --
2015-06-29 14:49 permissions dark.star777-NKkJACngtoFBDgjK7y7TUQ
[not found] <454655BC.30606@blueyonder.co.uk>
[not found] ` <20061030213355.GA25496@cloud.net.au>
[not found] ` <45469110.4070108@blueyonder.co.uk>
[not found] ` <20061031012432.GA6698@cloud.net.au>
2006-10-31 10:50 ` permissions richard
2002-07-08 8:04 permissions Nicolas Brainez
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=4C0A19FE.1020802@wpursell.net \
--to=bill.pursell@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 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.