git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Bagas Sanjaya <bagasdotme@gmail.com>
To: Nathan Neulinger <nneul@neulinger.org>, git@vger.kernel.org
Subject: Re: Recent changes for the unsafe directory handling - TINY improvement requested in error output
Date: Wed, 20 Apr 2022 13:16:57 +0700	[thread overview]
Message-ID: <e689bb30-dc7f-6e3d-a8d5-864e00de59d4@gmail.com> (raw)
In-Reply-To: <ec588ff7-b300-bc3a-b51c-67d190b27e9b@neulinger.org>

On 4/19/22 18:26, Nathan Neulinger wrote:
> However, if you do a 'git diff' - such as what you might naturally do right before attempting a 'git commit' - you do NOT get any useful response:
> 
>   root@SERVER:/local/APPNAME/bin# git diff
>   warning: Not a git repository. Use --no-index to compare two paths outside a working tree
>   usage: git diff --no-index [<options>] <path> <path>
>   ...snip-long-diff-help...
> 
> Please consider a small improvement to have the git diff help output (if displayed due to the repo exclusion warning) - ALSO display the 'git config' suggestion at the end of the output, instead of me having to remember - oh, go issue status to get the command hint to go set the exclusion. Would also be useful to have the git diff output do the same 'unsafe repository' message about ownership.
> 

I assumed that you have /local/APPNAME/bin shared by users (maybe via
NFS or something else), right?

I agreed with your suggestion. Also, I think usage help for git diff
in this case just add noise.

-- 
An old man doll... just what I always wanted! - Clara

  reply	other threads:[~2022-04-20  6:17 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-04-19 11:26 Recent changes for the unsafe directory handling - TINY improvement requested in error output Nathan Neulinger
2022-04-20  6:16 ` Bagas Sanjaya [this message]
2022-04-20 13:29   ` Nathan Neulinger

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=e689bb30-dc7f-6e3d-a8d5-864e00de59d4@gmail.com \
    --to=bagasdotme@gmail.com \
    --cc=git@vger.kernel.org \
    --cc=nneul@neulinger.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 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).