git.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Mike Coleman" <tutufan@gmail.com>
To: "Junio C Hamano" <gitster@pobox.com>
Cc: git@vger.kernel.org
Subject: Re: bug: git-diff silently fails when run outside of a repository (v1.5.4.2)
Date: Tue, 29 Apr 2008 18:03:08 -0500	[thread overview]
Message-ID: <3c6c07c20804291603q4fbe957eq3e3da39d4a2e29c0@mail.gmail.com> (raw)
In-Reply-To: <7vabjc5l3r.fsf@gitster.siamese.dyndns.org>

Oh, I didn't realize that.  It doesn't seem to be mentioned on the man
page, though I can't necessarily claim that I would have seen it if it
had.

Even so, this seems like a bug.  If I do this:

    $ cd /
    $ git-diff

there is no error message and no error status.  A diagnostic would be
very helpful.

Mike



On Tue, Apr 29, 2008 at 5:53 PM, Junio C Hamano <gitster@pobox.com> wrote:
> "Mike Coleman" <tutufan@gmail.com> writes:
>
>  > At least in version 1.5.4.2, git-diff silently fails when not run
>  > inside a repository.  It should give an error diagnostic, especially
>  > since "no output" would otherwise be a meaningful response.
>
>  Unfortunately this does not have enough information to go by, as unlike
>  many other programs, "git diff" contains a hack to be usable as a better
>  (for certain definition of "better" I may not necessarily agree with) GNU
>  diff replacement when run outside a repository.
>
>  i.e.
>
>         mkdir -p /var/tmp/junk
>         cd /var/tmp/junk
>         rm -fr .git ;# make sure it is not a repository
>         echo >a hello
>         echo >b world
>         git diff --color a b
>
>  is supposed to work.
>

  reply	other threads:[~2008-04-29 23:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-04-29 20:04 bug: git-diff silently fails when run outside of a repository (v1.5.4.2) Mike Coleman
2008-04-29 22:53 ` Junio C Hamano
2008-04-29 23:03   ` Mike Coleman [this message]
2008-04-29 23:37     ` Junio C Hamano
2008-04-30  0:56       ` Johannes Schindelin
2008-04-30  1:28         ` Junio C Hamano
2008-04-30  8:34           ` Johannes Schindelin

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=3c6c07c20804291603q4fbe957eq3e3da39d4a2e29c0@mail.gmail.com \
    --to=tutufan@gmail.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).