From: Johannes Sixt <j.sixt@viscovery.net>
To: Federico Lucifredi <federico@canonical.com>
Cc: git@vger.kernel.org
Subject: Re: Git Bug report
Date: Wed, 05 Oct 2011 08:11:37 +0200 [thread overview]
Message-ID: <4E8BF519.8090509@viscovery.net> (raw)
In-Reply-To: <1317763443.17036.15.camel@skyplex>
Am 10/4/2011 23:24, schrieb Federico Lucifredi:
> Hello Git list,
> Found a minor bug in git today - the error message reported is not
> correct when trying to access a repo that is not accessible
> permission-wise:
>
>> federico@skyplex:/etc$ git log
>> fatal: Not a git repository (or any of the parent directories): .git
>
> with correct access permissions, everything works as expected.
And the correct error message is...?
>> drwx------ 8 root root 4096 2011-10-03 16:53 .git
Assuming that you expected something like this:
fatal: .git: permission denied
it is hard to argue that a directory that happens to be named .git, but
was sealed by its owner should be assumed to be a git repository, albeit
one that we do not have access to. "Not a git repository" is an equally
justifyable error message, IMHO.
-- Hannes
next prev parent reply other threads:[~2011-10-05 6:11 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-04 21:24 Git Bug report Federico Lucifredi
2011-10-05 6:11 ` Johannes Sixt [this message]
2011-10-05 8:17 ` [PATCH] Report errors related to .git access during repository discovery Nguyễn Thái Ngọc Duy
2011-10-05 18:32 ` Git Bug report Federico Lucifredi
2011-10-05 7:22 ` Fredrik Gustafsson
2011-10-05 16:49 ` Junio C Hamano
2011-10-05 21:56 ` Nguyen Thai Ngoc Duy
2011-10-06 0:33 ` SZEDER Gábor
2011-10-06 0:44 ` Junio C Hamano
2011-10-06 1:09 ` SZEDER Gábor
[not found] ` <CABURp0qCsKG2oOxLw4BfU8UM=9V+pigd69ZK=TZVwetBPqjuiA@mail.gmail.com>
2011-10-06 16:22 ` Junio C Hamano
2011-10-06 16:26 ` Matthieu Moy
2011-10-06 16:54 ` Phil Hord
2011-10-06 22:57 ` Aaron Schrab
2011-10-06 16:48 ` Phil Hord
-- strict thread matches above, loose matches on Subject: below --
2022-04-14 7:22 Git Bug Report Randall Alfaro
2022-10-10 23:09 Git bug report Camden Narzt
2023-08-04 16:46 git " Paul Watson
2023-08-04 17:28 ` rsbecker
2023-08-08 17:07 ` Junio C Hamano
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=4E8BF519.8090509@viscovery.net \
--to=j.sixt@viscovery.net \
--cc=federico@canonical.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.