From: Ramkumar Ramachandra <artagnon@gmail.com>
Date: Thu, 04 Apr 2013 22:18:17 GMT
Subject: Re: [RFC/PATCH 0/7] Rework git core for native submodules
Message-ID: <CALkWK0kQ8qYXHKr4e93A1dh3Y1vL+HZvMR_1xtKkUr-_7bMS6Q@mail.gmail.com>
In-Reply-To: <7vd2uagd10.fsf@alter.siamese.dyndns.org>

Junio C Hamano wrote:
> When you are changing information _about_ submodules (e.g. you may
> be updating the recommended URL to fetch it from), you can use the
> usual tools like "git diff" to see how it changed, just like changes
> to any other file.  If the information _about_ a submodule A is
> stored at path A, and at the same time you have a working tree that
> corresponds to the root of the submodule A at that path, it gets
> unclear what "git diff A" should report.  Should it report the
> change in the submodule itself, or should it report the change in
> the information _about_ the submodule?  By separating these two
> concepts to two different places, .gitmodules design solves the
> issue nicely.

git diff-link.  Just turn it into a buffer and diff as usual.