# git whatchanged

4 messages from 2025-09-03 to 2025-09-03. Participants: Jesse Hathaway, Junio C Hamano, Kristoffer Haugsbakk.
Thread: https://gitlist.dev/t/64084

## Jesse Hathaway, 2025-09-03 15:34

Subject: git whatchanged
Message-ID: <CANSNSoWZNx3j3eLAayW64iC+bvC9XfetV+wZAkK6Zy8Zm0DWSw@mail.gmail.com>
URL: https://gitlist.dev/e/CANSNSoWZNx3j3eLAayW64iC%2BbvC9XfetV%2BwZAkK6Zy8Zm0DWSw%40mail.gmail.com

```
Git developers,

Thanks for the wonderful tool. I still use `git whatchanged` I realize
that `git log --raw` is the same output, but it doesn't have the same
mnemonic resonance as `git whatchanged`. So here is my small vote to
keep the feature. Yours kindly, Jesse Hathaway

```

## Junio C Hamano, 2025-09-03 19:56

Subject: Re: git whatchanged
Message-ID: <xmqqwm6fe2d9.fsf@gitster.g>
URL: https://gitlist.dev/e/xmqqwm6fe2d9.fsf%40gitster.g
In-Reply-To: <CANSNSoWZNx3j3eLAayW64iC+bvC9XfetV+wZAkK6Zy8Zm0DWSw@mail.gmail.com>

```
Jesse Hathaway <jesse@mbuki-mvuki.org> writes:

> Git developers,
>
> Thanks for the wonderful tool. I still use `git whatchanged` I realize
> that `git log --raw` is the same output, but it doesn't have the same
> mnemonic resonance as `git whatchanged`.

The "raw" output spews meaningless hexadecimal strings.  Why not
learn to use a more meaningful option, now you are switching out of
the command that is going away anyway, perhaps like "--status",
which lets you see the extent of damage to each path, for example?

```

## Kristoffer Haugsbakk, 2025-09-03 20:43

Subject: Re: git whatchanged
Message-ID: <0219828e-4f7b-418d-9d5e-87c0b5fbd4d1@app.fastmail.com>
URL: https://gitlist.dev/e/0219828e-4f7b-418d-9d5e-87c0b5fbd4d1%40app.fastmail.com
In-Reply-To: <xmqqwm6fe2d9.fsf@gitster.g>

```
On Wed, Sep 3, 2025, at 21:56, Junio C Hamano wrote:a
> The "raw" output spews meaningless hexadecimal strings.  Why not
> learn to use a more meaningful option, now you are switching out of
> the command that is going away anyway, perhaps like "--status",

* --stat

Probably.

> which lets you see the extent of damage to each path, for example?

-- 
Kristoffer Haugsbakk


```

## Junio C Hamano, 2025-09-03 21:47

Subject: Re: git whatchanged
Message-ID: <xmqqa53bdx90.fsf@gitster.g>
URL: https://gitlist.dev/e/xmqqa53bdx90.fsf%40gitster.g
In-Reply-To: <0219828e-4f7b-418d-9d5e-87c0b5fbd4d1@app.fastmail.com>

```
"Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail.com> writes:

> On Wed, Sep 3, 2025, at 21:56, Junio C Hamano wrote:a
>> The "raw" output spews meaningless hexadecimal strings.  Why not
>> learn to use a more meaningful option, now you are switching out of
>> the command that is going away anyway, perhaps like "--status",
>
> * --stat
>
> Probably.

Indeed.  Thanks for correcting me.  These days I use --compact-summary
instead myself, though ;-)

>
>> which lets you see the extent of damage to each path, for example?

```