From: Jeff King <peff@peff.net>
To: Sebastian Schuberth <sschuberth@gmail.com>
Cc: git@vger.kernel.org, Stefan Beller <sbeller@google.com>
Subject: Re: diff.ignoreSubmoudles config setting broken?
Date: Wed, 8 Mar 2017 08:33:48 -0500 [thread overview]
Message-ID: <20170308133348.2ovfsi44vq2rpgom@sigill.intra.peff.net> (raw)
In-Reply-To: <5e5b1b92-f7c6-2987-356e-1aab2bff557e@gmail.com>
On Wed, Mar 08, 2017 at 01:54:02PM +0100, Sebastian Schuberth wrote:
> I'm getting
>
> $ git config --global diff.ignoreSubmodules all
> $ git diff
> diff --git a/scanners/scancode-toolkit b/scanners/scancode-toolkit
> index 65e5c9c..6b021a8 160000
> --- a/scanners/scancode-toolkit
> +++ b/scanners/scancode-toolkit
> @@ -1 +1 @@
> -Subproject commit 65e5c9c9508441c5f62beff4749cf455c6eadc30
> +Subproject commit 6b021a8addf6d3c5f2a6ef1af6245e095c21d8ec
>
> but with
>
> $ git diff --ignore-submodules=all
Hrm. Isn't "all" the default? That's what git-diff(1) says (but I've
never used the feature myself).
That would imply to me that there's another config option set somewhere
(perhaps in the repo-level config). What does:
git config --show-origin --get-all diff.ignoresubmodules
say?
-Peff
next prev parent reply other threads:[~2017-03-08 14:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-08 12:54 diff.ignoreSubmoudles config setting broken? Sebastian Schuberth
2017-03-08 13:33 ` Jeff King [this message]
2017-03-08 13:43 ` Sebastian Schuberth
2017-03-08 14:01 ` Jeff King
2017-03-08 15:07 ` Sebastian Schuberth
2017-03-08 19:04 ` Stefan Beller
2017-03-08 20:54 ` Junio C Hamano
2017-03-08 22:11 ` Stefan Beller
2017-03-08 23:08 ` Junio C Hamano
2017-03-09 1:30 ` Stefan Beller
2017-03-09 16:15 ` Sebastian Schuberth
2017-03-08 22:27 ` Jacob Keller
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=20170308133348.2ovfsi44vq2rpgom@sigill.intra.peff.net \
--to=peff@peff.net \
--cc=git@vger.kernel.org \
--cc=sbeller@google.com \
--cc=sschuberth@gmail.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).