From: Alex Riesen <raa.lkml@gmail.com>
To: William Pursell <bill.pursell@gmail.com>
Cc: Andreas Schwab <schwab@linux-m68k.org>, git@vger.kernel.org
Subject: Re: permissions
Date: Sun, 6 Jun 2010 14:45:40 +0200 [thread overview]
Message-ID: <AANLkTim1-lN6TCD__V5F0BpPkmLbULkXHF03n0CqWTOi@mail.gmail.com> (raw)
In-Reply-To: <4C0B6C32.1090700@wpursell.net>
On Sun, Jun 6, 2010 at 11:36, William Pursell <bill.pursell@gmail.com> wrote:
> Alex Riesen wrote:
>> On Sat, Jun 5, 2010 at 20:23, William Pursell <bill.pursell@gmail.com> wrote:
>>> fatal: Not a git repository (or any of the parent directories): .git
>>>
>>> That's just weird. And if there is a git repository in a
>>> directory above, there may be great confusion, weeping
>>> and gnashing of teeth.
>>
>> How about just this? (I assume cwd does hold current working directory).
>
> <patch snipped>
>
> The problem is permissions, not that it's "not a git repository".
> The error message should be "permission denied".
Well, isn't it enough to diagnose the problem? (where it lies, at least).
next prev parent reply other threads:[~2010-06-06 12:45 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-05 9:33 permissions William Pursell
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 ` Alex Riesen [this message]
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
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
List information: http://vger.kernel.org/majordomo-info.html
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=AANLkTim1-lN6TCD__V5F0BpPkmLbULkXHF03n0CqWTOi@mail.gmail.com \
--to=raa.lkml@gmail.com \
--cc=bill.pursell@gmail.com \
--cc=git@vger.kernel.org \
--cc=schwab@linux-m68k.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.
Code repositories for project(s) associated with this public inbox
https://80x24.org/mirrors/git.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).