Git development
 help / color / mirror / Atom feed
From: Justin Sherrill <jsherril@redhat.com>
To: Kristoffer Haugsbakk <kristofferhaugsbakk@fastmail.com>,
	git@vger.kernel.org
Subject: Re: 'git whatchanged' is nominated for removal.
Date: Thu, 9 Oct 2025 17:09:27 -0400	[thread overview]
Message-ID: <bf5f59df-b390-411f-a187-c1da6cbfc1da@redhat.com> (raw)
In-Reply-To: <dc5de1b6-db24-499a-bee3-3eb2208ae08b@app.fastmail.com>

PERFECT!!! thank you :)

On 10/9/25 4:59 PM, Kristoffer Haugsbakk wrote:
> Good evening
>
> On Thu, Oct 9, 2025, at 22:53, Justin Sherrill wrote:
>> i recently got this message in my friendly git client:
>>
>> $ git wcp data/aws/insights-prod/account.yml
>> 'git whatchanged' is nominated for removal.
>> If you still use this command, please add an extra
>> option, '--i-still-use-this', on the command line
>> and let us know you still use it by sending an e-mail
>> to <git@vger.kernel.org>.  Thanks.
>> fatal: refusing to run without --i-still-use-this
>>
>> This is just me raising my hand as I still use this feature :)
> This command is being removed because it was supplanted by git-log(1) a
> long while ago. Both commands use the same machinery, just with
> different defaults.
>
> You can replce it with `git log`:
>
> • Given: `git whatchanged <opts>`
> • Replace with: `git log <opts> --no-merges --raw`
>
> Additionally for the sake of readability, you might have more
> use for `--stat` or `--name-only` rather than `--raw` if you are only
> reading the output (not feeding the output to another program).
>
-- 
Justin Sherrill
Content Sources Product Owner
Senior Principal Software Engineer


      reply	other threads:[~2025-10-09 21:09 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-09 20:53 'git whatchanged' is nominated for removal Justin Sherrill
2025-10-09 20:59 ` Kristoffer Haugsbakk
2025-10-09 21:09   ` Justin Sherrill [this message]

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=bf5f59df-b390-411f-a187-c1da6cbfc1da@redhat.com \
    --to=jsherril@redhat.com \
    --cc=git@vger.kernel.org \
    --cc=kristofferhaugsbakk@fastmail.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
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