git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Mohamed Akram <mohd.akram@outlook.com>
To: Junio C Hamano <gitster@pobox.com>
Cc: "git@vger.kernel.org" <git@vger.kernel.org>
Subject: Re: git diff prints long usage help if not run in git repo
Date: Tue, 23 Aug 2022 20:03:42 +0000	[thread overview]
Message-ID: <A01F00AA-B96E-40EF-9017-9005A8AC1E14@outlook.com> (raw)
In-Reply-To: <xmqq5yikcbd1.fsf@gitster.g>

I haven’t tried it but that patch seems to make sense to me, although I found
another related issue so it might need tweaking. When running `git diff` in a
repo owned by another user, the warning message says that this is not a git
repository, instead of the warning shown by other git commands about
"dubious ownership". To reproduce:

sudo mkdir repo
cd repo
sudo git init
git diff


      reply	other threads:[~2022-08-23 20:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-08-22 18:22 git diff prints long usage help if not run in git repo Mohamed Akram
2022-08-22 19:43 ` Junio C Hamano
2022-08-23 20:03   ` Mohamed Akram [this message]

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=A01F00AA-B96E-40EF-9017-9005A8AC1E14@outlook.com \
    --to=mohd.akram@outlook.com \
    --cc=git@vger.kernel.org \
    --cc=gitster@pobox.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).