git/list[1] front-page[2] threads[3] people[4] search[5] about
 

Re: confused git diff -G

From
APAlexei Podtelezhnikov <apodtele@gmail.com>
Date
Aug 25, 2023, 00:53 UTC
Message-ID
<CAJU=AjU6cggm+P3d_Ke4uyks79j7uYipbp0xPq7jJ+nCgNSUZg@mail.gmail.com>
In-Reply-To
<ZOfgKQfqvef9FXZ6@nand.local>
On Thu, Aug 24, 2023 at 6:56 PM Taylor Blau <me@ttaylorr.com> wrote:
Show 11 quoted lines
>
> On Thu, Aug 24, 2023 at 06:08:18PM -0400, Alexei Podtelezhnikov wrote:
> > I find this sections of the docs confusing:
> >
> > git diff -G (https://git.kernel.org/pub/scm/git/git.git/tree/Documentation/diff-options.txt#n656)
> >
> >  I do not follow why the example talks about `git log -G` and commits.
> > I see that thai file is included in git-log .txt but I do not
> > understand how to use git  diff -G.
>
> I agree that it can be somewhat confusing :-).
[skip to the practical example]
Show 12 quoted lines
> given to `-G`, like so:
>
>     $ git -C repo diff --stat HEAD^
>      a | 1 +
>      b | 1 +
>      2 files changed, 2 insertions(+)
>     $ git -C repo diff --stat HEAD^ -G a
>      a | 1 +
>      1 file changed, 1 insertion(+)
>     $ git -C repo diff --stat HEAD^ -G b
>      b | 1 +
>      1 file changed, 1 insertion(+)

Do you mean that-G is only useful to filter files and not the content of changes? That I can do without -G. Canyou give a better example?

Previous: Taylor BlauNext: Alexei Podtelezhnikov
Message 3 of 5 in “confused git diff -G”
  1. Alexei PodtelezhnikovAug 24, 2023
  2. Taylor BlauAug 24, 2023
  3. Alexei PodtelezhnikovAug 25, 2023
  4. Alexei PodtelezhnikovAug 25, 2023
  5. Junio C HamanoAug 25, 2023

Read the whole thread, see it on lore, or plain text.

$ cat FOOTERMessages come from the public archive at lore.kernel.org/git, fetched every hour. The front page is chosen and written each morning by an AI editor and can be wrong; the threads themselves are the record. About and API. For agents: an MCP server at https://gitlist.dev/mcp, and any thread, story or person page as Markdown by adding .md to its URL (or sending Accept: text/markdown). Details in /llms.txt.