From: Junio C Hamano <gitster@pobox•com>
To: jorg@ml1•net
Cc: git@vger•kernel.org
Subject: Re: Still using "git whatchanged"
Date: Tue, 02 Sep 2025 13:33:26 -0700 [thread overview]
Message-ID: <xmqqa53cioh5.fsf@gitster.g> (raw)
In-Reply-To: <6597b201-8087-462e-adc0-0ddaa8a7402e@app.fastmail.com> (jorg@ml1.net's message of "Tue, 02 Sep 2025 19:38:31 +0300")
jorg@ml1•net writes:
> On Tue, Sep 2, 2025, at 19:29, Junio C Hamano wrote:
>> jorg@ml1•net writes:
>>
>>> apart from what's stated in the subject, I think it's not logical
>>> to use "--raw" when I want to see what has changed.
>>>
>>> "git log" shows me the log. What's the raw part about wanting to
>>> see what's changed?
>>
>> But that is what "git whatchanged" gives, so when one is so attached to
>> what "git whatchanged" does, "--raw" is what we cite as "compatible"
>> option.
>
> My point was merely that IMO "raw" is not the best name for that
> option. When I specify "--raw" on the command line, I usually
> expect the program to output similar data than without that
> option, but of a less refined state or kind.
Sorry, but you are 20 years too late for *that* party. Once you
invent a time machine and go back 20 years, you can advocate for
different name(s) that may fit your personal preferences better
there.
But not here and not now.
next prev parent reply other threads:[~2025-09-02 20:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-02 6:18 Still using "git whatchanged" jorg
2025-09-02 16:29 ` Junio C Hamano
2025-09-02 16:38 ` jorg
2025-09-02 20:33 ` Junio C Hamano [this message]
2025-09-03 6:11 ` jorg
2025-09-03 7:08 ` Kristoffer Haugsbakk
2025-09-03 7:15 ` jorg
-- strict thread matches above, loose matches on Subject: below --
2025-10-15 5:42 still using 'git whatchanged' Greg Couch
2025-10-15 7:22 ` Kristoffer Haugsbakk
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=xmqqa53cioh5.fsf@gitster.g \
--to=gitster@pobox$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=jorg@ml1$(echo .)net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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