From: "Jose Jaramillo" <joseph@devjj•com>
To: "Kristoffer Haugsbakk" <kristofferhaugsbakk@fastmail•com>,
git@vger•kernel.org
Subject: Re: git whatchanged
Date: Wed, 10 Sep 2025 14:15:39 -0700 [thread overview]
Message-ID: <25f1da6b-75af-4255-8367-3fb6a4f778e6@app.fastmail.com> (raw)
In-Reply-To: <acc2d65c-a050-4792-be3c-83a00810f105@app.fastmail.com>
That's super helpful, thank you!
On Wed, Sep 10, 2025, at 2:03 PM, Kristoffer Haugsbakk wrote:
> Hi
>
> On Wed, Sep 10, 2025, at 22:49, Jose Jaramillo wrote:
> > I still use this! ~J
>
> You can replace it with `git log`:
>
> • Given: `git whatchanged <opts>`
> • Replace with: `git log <opts> --no-merges --raw`
>
> And get basically the same output.
>
> Or you can use some more modern options to git-log(1) that are more
> likely to be suitable for your needs:
>
> https://lore.kernel.org/git/xmqq8qimrrxo.fsf@gitster.g/T/#md4350a5c8cd15dc5515f140f8a4d65cd86843584
>
> --
> Kristoffer Haugsbakk
>
next prev parent reply other threads:[~2025-09-10 21:16 UTC|newest]
Thread overview: 39+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-10 20:49 git whatchanged Jose Jaramillo
2025-09-10 21:03 ` Kristoffer Haugsbakk
2025-09-10 21:15 ` Jose Jaramillo [this message]
-- strict thread matches above, loose matches on Subject: below --
2025-11-07 11:40 Franz Brauße
2025-11-07 13:11 ` Kristoffer Haugsbakk
2025-11-07 14:16 ` Franz Brauße
2025-11-07 14:30 ` Kristoffer Haugsbakk
2025-10-31 8:02 Remke Schuurmans
2025-10-31 8:23 ` Kristoffer Haugsbakk
[not found] ` <c2551c49-bcb4-4518-97d3-063941d591e8@gmail.com>
2025-10-31 9:13 ` Kristoffer Haugsbakk
2025-10-16 12:16 Julian Squires
2025-10-16 13:27 ` Kristoffer Haugsbakk
2025-10-13 12:44 Grzegorz Koperwas
2025-10-13 13:47 ` Kristoffer Haugsbakk
2025-10-08 14:20 Git whatchanged Filippo Falezza
2025-10-08 14:42 ` Kristoffer Haugsbakk
2025-10-02 6:48 git whatchanged Jiří Bašek
2025-10-02 7:12 ` Kristoffer Haugsbakk
2025-09-26 1:00 Neal Miller
2025-09-26 7:13 ` Kristoffer Haugsbakk
2025-09-26 15:54 ` Junio C Hamano
2025-09-28 1:12 ` Neal Miller
2025-09-04 23:45 Michael Tourigny (TERAWE CORPORATION)
2025-09-03 15:34 Jesse Hathaway
2025-09-03 19:56 ` Junio C Hamano
2025-09-03 20:43 ` Kristoffer Haugsbakk
2025-09-03 21:47 ` Junio C Hamano
2025-08-26 13:04 Chris Palmer
2025-08-26 13:54 ` Kristoffer Haugsbakk
2025-08-19 17:51 Chris Judkins-Fisher
2025-08-19 17:59 ` Chris Judkins-Fisher
2025-08-19 20:57 ` rsbecker
2025-08-20 7:52 ` Kristoffer Haugsbakk
2025-08-20 14:12 ` rsbecker
2025-08-20 16:49 ` Junio C Hamano
2025-08-20 17:05 ` Chris Judkins-Fisher
2025-08-20 20:58 ` Kristoffer Haugsbakk
2025-08-20 21:10 ` Junio C Hamano
2025-08-20 21:11 ` 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=25f1da6b-75af-4255-8367-3fb6a4f778e6@app.fastmail.com \
--to=joseph@devjj$(echo .)com \
--cc=git@vger$(echo .)kernel.org \
--cc=kristofferhaugsbakk@fastmail$(echo .)com \
/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